mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/2] riscv: use generic bitsperlong.h
Date: Mon, 12 Aug 2019 09:02:31 +0200	[thread overview]
Message-ID: <20190812070231.rqwbytsywcumzyok@pengutronix.de> (raw)
In-Reply-To: <20190807163046.6160-1-yamada.masahiro@socionext.com>

On Thu, Aug 08, 2019 at 01:30:45AM +0900, Masahiro Yamada wrote:
> Linux highly depends on the fact that the 'long' and the pointer
> have the same width, and so does barebox.
> 
> So, we can always use include/asm-generic/bitsperlong.h, which
> determines BITS_PER_LONG depending on CONFIG_64BIT.
> 
> This is what Linux does (at least in the kernel-space), and barebox
> can follow it.
> 
> Currently, barebox only supports 32-bit riscv, but this should work
> when it supports 64-bit by adding CONFIG_64BIT to arch/riscv/Kconfig.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>  arch/riscv/include/asm/bitsperlong.h | 11 +----------
>  1 file changed, 1 insertion(+), 10 deletions(-)

Applied, thanks

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      parent reply	other threads:[~2019-08-12  7:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 16:30 Masahiro Yamada
2019-08-07 16:30 ` [PATCH 2/2] mips: " Masahiro Yamada
2019-08-12  7:02 ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190812070231.rqwbytsywcumzyok@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox