From: Greg KH <gregkh@linuxfoundation.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Max Gurtovoy <maxg@mellanox.com>,
matanb@mellanox.com, leon@leon.nu, sagi@grimberg.me,
linux-rdma@vger.kernel.org, stable@vger.kernel.org,
robert@leblancnet.us
Subject: Re: [PATCH] IB/core: Fix bit curruption in ib_device_cap_flags structure
Date: Thu, 2 Jun 2016 09:52:26 -0700 [thread overview]
Message-ID: <20160602165226.GA30960@kroah.com> (raw)
In-Reply-To: <c72fac21-0a3d-fc40-ec82-e156f29c2fab@sandisk.com>
On Thu, Jun 02, 2016 at 09:41:03AM -0700, Bart Van Assche wrote:
> On 06/02/2016 09:24 AM, Greg KH wrote:
> > On Thu, Jun 02, 2016 at 12:28:05PM +0300, Max Gurtovoy wrote:
> > > diff --git a/include/rdma/ib_verbs.h b/include/rdma/ib_verbs.h
> > > index 432bed5..c97357b 100644
> > > --- a/include/rdma/ib_verbs.h
> > > +++ b/include/rdma/ib_verbs.h
> > > @@ -217,7 +217,7 @@ enum ib_device_cap_flags {
> > > IB_DEVICE_CROSS_CHANNEL = (1 << 27),
> > > IB_DEVICE_MANAGED_FLOW_STEERING = (1 << 29),
> > > IB_DEVICE_SIGNATURE_HANDOVER = (1 << 30),
> > > - IB_DEVICE_ON_DEMAND_PAGING = (1 << 31),
> > > + IB_DEVICE_ON_DEMAND_PAGING = (1ULL << 31),
> > > IB_DEVICE_SG_GAPS_REG = (1ULL << 32),
> > > IB_DEVICE_VIRTUAL_FUNCTION = ((u64)1 << 33),
> > > IB_DEVICE_RAW_SCATTER_FCS = ((u64)1 << 34),
> >
> > Why not just use the BIT() and BIT_ULL() macros instead of "open coding"
> > these?
>
> Hi Greg,
>
> Are you sure that these macros are useful?
Yes.
> My personal opinion is that these macros makes code harder to read
> instead of easier. I'd like to see these macros disappear.
Sorry but we are converting the whole kernel to use them, I suggest you
get used to them :)
greg k-h
next prev parent reply other threads:[~2016-06-02 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 9:28 [PATCH] IB/core: Fix bit curruption in ib_device_cap_flags structure Max Gurtovoy
2016-06-02 11:33 ` Christoph Hellwig
2016-06-02 11:48 ` Max Gurtovoy
2016-06-02 11:56 ` Sagi Grimberg
2016-06-02 16:51 ` Jason Gunthorpe
2016-06-02 16:24 ` Greg KH
2016-06-02 16:41 ` Bart Van Assche
2016-06-02 16:52 ` Greg KH [this message]
2016-06-02 16:41 ` Max Gurtovoy
2016-06-02 16:52 ` Greg KH
2016-06-02 16:48 ` Christoph Lameter
2016-06-02 16:52 ` Jason Gunthorpe
2016-06-03 10:47 ` Leon Romanovsky
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=20160602165226.GA30960@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bart.vanassche@sandisk.com \
--cc=leon@leon.nu \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=maxg@mellanox.com \
--cc=robert@leblancnet.us \
--cc=sagi@grimberg.me \
--cc=stable@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