linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org,
	linux-bcache@vger.kernel.org, netdev@vger.kernel.org,
	linux-scsi@vger.kernel.org, logfs@logfs.org
Cc: dmaengine@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-s390@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: [PATCH 00/12] treewide: Use DECLARE_BITMAP
Date: Tue, 19 May 2015 18:37:48 -0700	[thread overview]
Message-ID: <cover.1432085659.git.joe@perches.com> (raw)

Use the standard method to declare a bitmap array.

Joe Perches (12):
  ARM: mach-imx: iomux-imx31: Use DECLARE_BITMAP
  dmaengine: rcar-dmac: Use DECLARE_BITMAP
  drm/amdkfd: Use DECLARE_BITMAP
  drm/radeon: Use DECLARE_BITMAP
  IB/ehca: Use DECLARE_BITMAP
  bcache: Use DECLARE_BITMAP
  spider_net: Use DECLARE_BITMAP
  s390/sclp: Use DECLARE_BITMAP
  [SCSI] qla4xxx: Use DECLARE_BITMAP
  scsi: Use DECLARE_BITMAP
  logfs: Use DECLARE_BITMAP
  sunrpc: Use DECLARE_BITMAP

 arch/arm/mach-imx/iomux-imx31.c           | 2 +-
 drivers/dma/sh/rcar-dmac.c                | 2 +-
 drivers/gpu/drm/amd/amdkfd/kfd_priv.h     | 5 ++---
 drivers/gpu/drm/radeon/radeon.h           | 2 +-
 drivers/infiniband/hw/ehca/ipz_pt_fn.h    | 2 +-
 drivers/md/bcache/journal.c               | 2 +-
 drivers/net/ethernet/toshiba/spider_net.c | 3 +--
 drivers/s390/char/sclp_cmd.c              | 2 +-
 drivers/scsi/qla4xxx/ql4_def.h            | 2 +-
 drivers/scsi/sr.c                         | 2 +-
 fs/logfs/logfs.h                          | 2 +-
 net/sunrpc/auth_gss/svcauth_gss.c         | 2 +-
 12 files changed, 13 insertions(+), 15 deletions(-)

-- 
2.1.2

             reply	other threads:[~2015-05-20  1:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:37 Joe Perches [this message]
2015-05-20  1:37 ` [PATCH 08/12] s390/sclp: Use DECLARE_BITMAP Joe Perches
2015-05-20  7:03   ` Heiko Carstens

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=cover.1432085659.git.joe@perches.com \
    --to=joe@perches.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=logfs@logfs.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).