linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: David Frey <dpfrey@gmail.com>, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: chemical: bme680: Remove field value defines
Date: Sat, 25 Aug 2018 09:14:24 +0100	[thread overview]
Message-ID: <20180825091424.75ddad60@archlinux> (raw)
In-Reply-To: <20180822104405.GA26015@himanshu-Vostro-3559>

On Wed, 22 Aug 2018 16:14:05 +0530
Himanshu Jha <himanshujha199640@gmail.com> wrote:

> On Mon, Aug 20, 2018 at 10:39:59AM -0700, David Frey wrote:
> > Remove BME680_RUN_GAS_EN_BIT and BME680_NB_CONV_0_VAL field value
> > definitions because the fields are simply boolean and integer
> > respectively.
> > 
> > Signed-off-by: David Frey <dpfrey@gmail.com>  
> Reviewed-by: Himanshu Jha <himanshujha199640@gmail.com>
> Tested-by: Himanshu Jha <himanshujha199640@gmail.com>

Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.

Thanks,

Jonathan

> 
> > ---
> > This patch applies on top of my "indent #defines consistently" v3 patch.
> > Appologies if I should have submitted this patch in a different way.  If
> > I should have submitted this differently, I would appreciate a pointer
> > on what I should have done in this case.  
> 
> This applies cleanly so no worries I guess.
> Would have been better to send this patch as a separate thread since
> thread becomes complex and its hard to find the new patch in the
> nested series of replies.
> 
> > BME680_RUN_GAS_EN_BIT was indeed somewhat wrongly formatted, but the
> > issue was not the indentation level, but rather that I should have
> > followed immediately after BME680_RUN_GAS_MASK.  Once I moved it there,
> > I realized that neither this definition nor BME680_NB_CONV_0_VAL really
> > added any value and hence I removed both in this patch.  
> 
> My main intention was to make it explicit that we are selected NB_CONV_0
> set point, and I didn't knew about FIELD_PREP helper macro until you
> pointed me out in the early review cycle.
> 
> Now, it is much appropriate.
> 
> Thanks

  reply	other threads:[~2018-08-25 11:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 19:03 [PATCH v3 0/7] bme680 cleanup David Frey
2018-08-17 19:03 ` [PATCH v3 1/7] iio: chemical: bme680: use clamp macro David Frey
2018-08-18 11:03   ` Himanshu Jha
2018-08-19 15:47     ` Jonathan Cameron
2018-08-20 17:18       ` David Frey
2018-08-20 17:55         ` Himanshu Jha
2018-08-20 17:58         ` Jonathan Cameron
2018-08-17 19:03 ` [PATCH v3 2/7] iio: chemical: bme680: cleanup bme680_read_calib formatting David Frey
2018-08-18 11:06   ` Himanshu Jha
2018-08-19 15:54     ` Jonathan Cameron
2018-08-19 17:18       ` Himanshu Jha
2018-08-20 19:24     ` David Frey
2018-08-21 18:46       ` Himanshu Jha
2018-08-17 19:03 ` [PATCH v3 3/7] iio: chemical: bme680: indent #defines consistently David Frey
2018-08-18 11:07   ` Himanshu Jha
2018-08-19 16:02     ` Jonathan Cameron
2018-08-19 17:28       ` Himanshu Jha
2018-08-19 19:14         ` Jonathan Cameron
2018-08-20 15:37           ` Himanshu Jha
2018-08-20 17:39           ` [PATCH] iio: chemical: bme680: Remove field value defines David Frey
2018-08-22 10:44             ` Himanshu Jha
2018-08-25  8:14               ` Jonathan Cameron [this message]
2018-08-17 19:03 ` [PATCH v3 4/7] iio: chemical: bme680: change MSK->MASK in #defines David Frey
2018-08-18 11:09   ` Himanshu Jha
2018-08-19 16:05     ` Jonathan Cameron
2018-08-17 19:03 ` [PATCH v3 5/7] iio: chemical: bme680: use GENMASK macro David Frey
2018-08-18 11:09   ` Himanshu Jha
2018-08-19 16:07     ` Jonathan Cameron
2018-08-17 19:03 ` [PATCH v3 6/7] iio: chemical: bme680: use FIELD_GET macro David Frey
2018-08-18 11:10   ` Himanshu Jha
2018-08-19 16:08     ` Jonathan Cameron
2018-08-17 19:03 ` [PATCH v3 7/7] iio: chemical: bme680: simplify oversampling handling David Frey
2018-08-18 11:17   ` Himanshu Jha
2018-08-19 16:14     ` Jonathan Cameron

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=20180825091424.75ddad60@archlinux \
    --to=jic23@kernel.org \
    --cc=dpfrey@gmail.com \
    --cc=himanshujha199640@gmail.com \
    --cc=linux-iio@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).