From: Shraddha Barke <shraddha.6596@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Julia Lawall <julia.lawall@lip6.fr>,
Hartmut Knaack <knaack.h@gmx.de>,
Andreas Dilger <andreas.dilger@intel.com>,
Ian Abbott <abbotti@mev.co.uk>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] Staging: iio: cdc: Prefer using the BIT macro
Date: Sat, 12 Sep 2015 16:47:23 +0530 [thread overview]
Message-ID: <CAO393ABYMQof2s-R3E1GPS5c9OZDFN_VhidCaXS6HHULcd0zXg@mail.gmail.com> (raw)
In-Reply-To: <55F3F49D.9000201@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
On Sat, Sep 12, 2015 at 3:17 PM, Jonathan Cameron <jic23@kernel.org> wrote:
> On 10/09/15 17:32, Shraddha Barke wrote:
> > This patch replaces bit shifting on 1 with the BIT(x) macro
> >
> > This was done with coccinelle:
> > @@ int g; @@
> >
> > -(1 << g)
> > +BIT(g)
> >
> > Signed-off-by: Shraddha Barke <shraddha.6596@gmail.com>
> Something odd happened here as this is only a small proportion of the cases
> that should be updated in this file. There's one at the bottom of the
> patch for starters!
>
> I didn't apply BIT(x) for mixed cases.I think I should drop this patch
altogether but
Greg has added it. Will it cause problems ? :(
> This driver also uses a lot of cases of 0 shifted to represent
> the opposite state for a given bit in the register. The effective
> documentation provided by that is lost if we convert the bit set ones
> over like this. Might seem odd, but perhaps we need a ZERO(X) macro
> as well (which is of course always 0) to cover that approach.
>
> Jonathan
> > ---
> > drivers/staging/iio/cdc/ad7746.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/staging/iio/cdc/ad7746.c
> b/drivers/staging/iio/cdc/ad7746.c
> > index e6e9eaa..10fa372 100644
> > --- a/drivers/staging/iio/cdc/ad7746.c
> > +++ b/drivers/staging/iio/cdc/ad7746.c
> > @@ -46,10 +46,10 @@
> > #define AD7746_REG_VOLT_GAINL 18
> >
> > /* Status Register Bit Designations (AD7746_REG_STATUS) */
> > -#define AD7746_STATUS_EXCERR (1 << 3)
> > -#define AD7746_STATUS_RDY (1 << 2)
> > -#define AD7746_STATUS_RDYVT (1 << 1)
> > -#define AD7746_STATUS_RDYCAP (1 << 0)
> > +#define AD7746_STATUS_EXCERR BIT(3)
> > +#define AD7746_STATUS_RDY BIT(2)
> > +#define AD7746_STATUS_RDYVT BIT(1)
> > +#define AD7746_STATUS_RDYCAP BIT(0)
> >
> > /* Capacitive Channel Setup Register Bit Designations
> (AD7746_REG_CAP_SETUP) */
> > #define AD7746_CAPSETUP_CAPEN (1 << 7)
> >
>
>
[-- Attachment #2: Type: text/html, Size: 2878 bytes --]
next prev parent reply other threads:[~2015-09-12 11:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 16:32 [PATCH 4/6] Staging: iio: cdc: Prefer using the BIT macro Shraddha Barke
2015-09-10 16:32 ` [PATCH 5/6] Staging: lustre: ptlrpc: " Shraddha Barke
2015-09-10 16:32 ` [PATCH 6/6] Staging: comedi: " Shraddha Barke
2015-09-12 9:47 ` [PATCH 4/6] Staging: iio: cdc: " Jonathan Cameron
2015-09-12 11:17 ` Shraddha Barke [this message]
2015-09-12 15:49 ` Greg Kroah-Hartman
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=CAO393ABYMQof2s-R3E1GPS5c9OZDFN_VhidCaXS6HHULcd0zXg@mail.gmail.com \
--to=shraddha.6596@gmail.com \
--cc=abbotti@mev.co.uk \
--cc=andreas.dilger@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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).