From: "Dilger, Andreas" <andreas.dilger@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jaya Durga <rjdurga@gmail.com>,
"Drokin, Oleg" <oleg.drokin@intel.com>,
"jsimmons@infradead.org" <jsimmons@infradead.org>,
"Hammond, John" <john.hammond@intel.com>,
"bobijam@hotmail.com" <bobijam@hotmail.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 8/8] Staging: lustre :lustre: include :lustre_compat.h: Prefer using the BIT macro
Date: Wed, 12 Jul 2017 05:13:11 +0000 [thread overview]
Message-ID: <326250A0-4785-40C4-BA11-2D708815039B@intel.com> (raw)
In-Reply-To: <20170711170818.GA5013@kroah.com>
> On Jul 11, 2017, at 11:08, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Jul 06, 2017 at 12:43:15PM +0530, Jaya Durga wrote:
>> Replace all instances of (1 << 27) with BIT(27) to fix
>> checkpatch check messages
>>
>> Signed-off-by: Jaya Durga <rjdurga@gmail.com>
>> ---
>> drivers/staging/lustre/lustre/include/lustre_compat.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/lustre/lustre/include/lustre_compat.h b/drivers/staging/lustre/lustre/include/lustre_compat.h
>> index da9ce19..686a251 100644
>> --- a/drivers/staging/lustre/lustre/include/lustre_compat.h
>> +++ b/drivers/staging/lustre/lustre/include/lustre_compat.h
>> @@ -43,7 +43,7 @@
>> * set ATTR_BLOCKS to a high value to avoid any risk of collision with other
>> * ATTR_* attributes (see bug 13828)
>> */
>> -#define ATTR_BLOCKS (1 << 27)
>> +#define ATTR_BLOCKS BIT(27)
>
> Isn't this used in lustre's userspace code? If so, you can't use the
> BIT() macro there :(
>
> Please check before you redo this.
The "lustre_compat.h" header was previously used for compatibility between different kernel
versions, which is why it is now basically empty. It isn't used for userspace interfaces
as other "compat" headers are in the kernel.
Cheers, Andreas
--
Andreas Dilger
Lustre Principal Architect
Intel Corporation
prev parent reply other threads:[~2017-07-12 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 7:13 Jaya Durga
2017-07-06 7:23 ` Frans Klaver
2017-07-11 17:08 ` Greg KH
2017-07-12 5:13 ` Dilger, Andreas [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=326250A0-4785-40C4-BA11-2D708815039B@intel.com \
--to=andreas.dilger@intel.com \
--cc=bobijam@hotmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=john.hammond@intel.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lustre-devel@lists.lustre.org \
--cc=mingo@kernel.org \
--cc=oleg.drokin@intel.com \
--cc=rjdurga@gmail.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
all inboxes | Powered by JetHome®