From: Christoph Hellwig <hch@infradead.org>
To: Phong Tran <tranmanphong@gmail.com>
Cc: robh+dt@kernel.org, frowand.list@gmail.com,
pantelis.antoniou@konsulko.com, natechancellor@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: replace be32_to_cpu to be32_to_cpup
Date: Tue, 30 Apr 2019 06:32:31 -0700 [thread overview]
Message-ID: <20190430133231.GA5646@infradead.org> (raw)
In-Reply-To: <20190430090044.16345-1-tranmanphong@gmail.com>
On Tue, Apr 30, 2019 at 04:00:44PM +0700, Phong Tran wrote:
>
> diff --git a/include/linux/of.h b/include/linux/of.h
> index e240992e5cb6..1c35fc8f19b0 100644
> --- a/include/linux/of.h
> +++ b/include/linux/of.h
> @@ -235,7 +235,7 @@ static inline u64 of_read_number(const __be32 *cell, int size)
> {
> u64 r = 0;
> while (size--)
> - r = (r << 32) | be32_to_cpu(*(cell++));
> + r = (r << 32) | be32_to_cpup(cell++);
> return r;
This whole function looks odd. It could simply be replaced with
calls to get_unaligned_be64 / get_unaligned_be32. Given that we have a
lot of callers we can't easily do that, but at least we could try
something like
static inline u64 of_read_number(const __be32 *cell, int size)
{
WARN_ON_ONCE(size < 1);
WARN_ON_ONCE(size > 2);
if (size == 1)
return get_unaligned_be32(cell);
return get_unaligned_be64(cell);
}
next prev parent reply other threads:[~2019-04-30 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 9:00 [PATCH] of: replace be32_to_cpu to be32_to_cpup Phong Tran
2019-04-30 9:37 ` Nathan Chancellor
2019-04-30 10:52 ` David Laight
2019-04-30 14:56 ` [PATCH V2] of: fix clang -Wunsequenced for be32_to_cpu() Phong Tran
2019-04-30 16:28 ` Nick Desaulniers
2019-04-30 16:29 ` Nick Desaulniers
2019-05-01 18:13 ` Nick Desaulniers
2019-05-01 19:33 ` Rob Herring
2019-04-30 13:32 ` Christoph Hellwig [this message]
2019-04-30 14:44 ` [PATCH] of: replace be32_to_cpu to be32_to_cpup Phong Tran
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=20190430133231.GA5646@infradead.org \
--to=hch@infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=tranmanphong@gmail.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;
as well as URLs for NNTP newsgroup(s).