From: "H. Peter Anvin" <hpa@zytor.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] introduce lower_32_bits() macro
Date: Fri, 25 Jul 2008 12:06:27 -0400 [thread overview]
Message-ID: <4889FA03.6010708@zytor.com> (raw)
In-Reply-To: <1216998747-16896-1-git-send-email-joerg.roedel@amd.com>
Joerg Roedel wrote:
> The file kernel.h contains the upper_32_bits macro. This patch adds the other
> part, the lower_32_bits macro. Its first use will be in the driver for AMD
> IOMMU.
>
> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
> ---
> include/linux/kernel.h | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> index f9cd7a5..6fd2977 100644
> --- a/include/linux/kernel.h
> +++ b/include/linux/kernel.h
> @@ -73,6 +73,12 @@ extern const char linux_proc_banner[];
> */
> #define upper_32_bits(n) ((u32)(((n) >> 16) >> 16))
>
> +/**
> + * lower_32_bits - return bits 0-31 of a number
> + * @n: the number we're accessing
> + */
> +#define lower_32_bits(n) ((n) & 0xffffffffULL)
> +
NAK. These are assymmetric with regards to type, which is the *last*
thing we want.
The symmetric definition would be ((u32)(n)), but that's already
idiomatic use, so why not use it as-is?
-hpa
next prev parent reply other threads:[~2008-07-25 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 15:12 [PATCH] introduce lower_32_bits() macro Joerg Roedel
2008-07-25 16:06 ` H. Peter Anvin [this message]
2008-07-25 20:47 ` Andrew Morton
2008-07-25 20:54 ` Roland Dreier
2008-07-25 21:39 ` H. Peter Anvin
2008-07-25 20:54 ` H. Peter Anvin
2008-07-28 10:59 ` Joerg Roedel
2008-07-28 12:07 ` Joerg Roedel
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=4889FA03.6010708@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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