public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	benh@kernel.crashing.org, davem@davemloft.net,
	linux@rasmusvillemoes.dk
Subject: Re: [PATCH v2] iommu-common: Do not use 64 bit  constant 0xffffffffffffffffl for computing align_mask
Date: Tue, 21 Jul 2015 12:59:32 -0700	[thread overview]
Message-ID: <20150721195932.GA19668@roeck-us.net> (raw)
In-Reply-To: <20150721044941.GA24786@oracle.com>

On Tue, Jul 21, 2015 at 06:49:41AM +0200, Sowmini Varadhan wrote:
> Using a 64 bit constant generates "warning: integer constant is too
> large for 'long' type" on 32 bit platforms. Instead use ~0ul and
> BITS_PER_LONG.
> 
> Detected by Andrew Morton on ARMD.
> 
> Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>

Looks ok afaics.

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
> v2: use BITS_PER_LONG and ulong as discussed on mailing list.
> 
>  lib/iommu-common.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/lib/iommu-common.c b/lib/iommu-common.c
> index df30632..ff19f66 100644
> --- a/lib/iommu-common.c
> +++ b/lib/iommu-common.c
> @@ -119,7 +119,7 @@ unsigned long iommu_tbl_range_alloc(struct device *dev,
>  	unsigned long align_mask = 0;
>  
>  	if (align_order > 0)
> -		align_mask = 0xffffffffffffffffl >> (64 - align_order);
> +		align_mask = ~0ul >> (BITS_PER_LONG - align_order);
>  
>  	/* Sanity check */
>  	if (unlikely(npages == 0)) {
> -- 
> 1.7.1
> 

      reply	other threads:[~2015-07-21 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21  4:49 [PATCH v2] iommu-common: Do not use 64 bit constant 0xffffffffffffffffl for computing align_mask Sowmini Varadhan
2015-07-21 19:59 ` Guenter Roeck [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=20150721195932.GA19668@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=sowmini.varadhan@oracle.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