From: Greg KH <gregkh@linuxfoundation.org>
To: Shiva Kerdel <shiva@exdev.nl>
Cc: martyn@welchs.me.uk, manohar.vanga@gmail.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: vme: vme_pio2: Prefer using the BIT macro
Date: Mon, 7 Nov 2016 10:58:51 +0100 [thread overview]
Message-ID: <20161107095851.GA13009@kroah.com> (raw)
In-Reply-To: <20161105193111.4224-1-shiva@exdev.nl>
On Sat, Nov 05, 2016 at 08:31:11PM +0100, Shiva Kerdel wrote:
> Replace all occurences of (1 << x) by BIT(x) in the file vme_pio2.h to
> get rid of checkpatch.pl "check" output "Prefer using the BIT macro".
>
> Signed-off-by: Shiva Kerdel <shiva@exdev.nl>
> ---
> drivers/staging/vme/devices/vme_pio2.h | 86 +++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 43 deletions(-)
Someone else sent this same patch a few days before you did, sorry.
greg k-h
prev parent reply other threads:[~2016-11-07 9:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 19:31 [PATCH] Staging: vme: vme_pio2: Prefer using the BIT macro Shiva Kerdel
2016-11-07 9:58 ` Greg KH [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=20161107095851.GA13009@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=shiva@exdev.nl \
/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).