mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 01/12] ARM: mach-imx: iomux-imx31: Use DECLARE_BITMAP
Date: Wed, 20 May 2015 08:50:35 +0200	[thread overview]
Message-ID: <20150520065035.GO24769@pengutronix.de> (raw)
In-Reply-To: <04e6c29d921d20f6089dd5d13f2c35bbe362eb0e.1432085659.git.joe@perches.com>

Hello,

On Tue, May 19, 2015 at 06:37:49PM -0700, Joe Perches wrote:
> Use the generic mechanism to declare a bitmap instead of unsigned long.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>  arch/arm/mach-imx/iomux-imx31.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/mach-imx/iomux-imx31.c b/arch/arm/mach-imx/iomux-imx31.c
> index d6a3075..6dd22ca 100644
> --- a/arch/arm/mach-imx/iomux-imx31.c
> +++ b/arch/arm/mach-imx/iomux-imx31.c
> @@ -40,7 +40,7 @@ static DEFINE_SPINLOCK(gpio_mux_lock);
>  
>  #define IOMUX_REG_MASK (IOMUX_PADNUM_MASK & ~0x3)
>  
> -static unsigned long mxc_pin_alloc_map[NB_PORTS * 32 / BITS_PER_LONG];
> +static DECLARE_BITMAP(mxc_pin_alloc_map, NB_PORTS * 32);
>  /*
>   * set the mode for a IOMUX pin.
>   */
Compile tested and
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-05-20  6:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:37 [PATCH 00/12] treewide: " Joe Perches
2015-05-20  1:37 ` [PATCH 01/12] ARM: mach-imx: iomux-imx31: " Joe Perches
2015-05-20  6:50   ` Uwe Kleine-König [this message]
2015-05-21  1:09   ` Shawn Guo
2015-05-20  1:37 ` [PATCH 02/12] dmaengine: rcar-dmac: " Joe Perches
2015-05-25 17:12   ` Vinod Koul
2015-05-20  1:37 ` [PATCH 03/12] drm/amdkfd: " Joe Perches
2015-05-20  7:32   ` Oded Gabbay
2015-05-20  1:37 ` [PATCH 04/12] drm/radeon: " Joe Perches
2015-05-20 16:45   ` Alex Deucher
2015-05-20  1:37 ` [PATCH 05/12] IB/ehca: " Joe Perches
2015-05-20  1:37 ` [PATCH 06/12] bcache: " Joe Perches
2015-05-20  1:37 ` [PATCH 07/12] spider_net: " Joe Perches
2015-05-21 21:18   ` David Miller
2015-05-20  1:37 ` [PATCH 08/12] s390/sclp: " Joe Perches
2015-05-20  7:03   ` Heiko Carstens
2015-05-20  1:37 ` [PATCH 09/12] [SCSI] qla4xxx: " Joe Perches
2015-05-20 13:04   ` Nilesh Javali
2015-05-20  1:37 ` [PATCH 10/12] scsi: " Joe Perches
2015-05-20  5:03   ` Bart Van Assche
2015-05-20  1:37 ` [PATCH 11/12] logfs: " Joe Perches
2015-05-20  1:38 ` [PATCH 12/12] sunrpc: " Joe Perches
     [not found] ` <OF4147CCA9.838D5302-ONC1257E4B.000904D1-C1257E4B.000904DB@de.ibm.com>
2015-05-20  1:50   ` [possible PATCH -next] MAINTAINERS: Jens Axboe has changed email address Joe Perches
2015-05-20  3:48     ` Jens Axboe
2015-05-20  3:57       ` Joe Perches
2015-05-20 14:13         ` Jens Axboe

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=20150520065035.GO24769@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=joe@perches.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=shawn.guo@linaro.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

Powered by JetHome