From: David Frey <dpfrey@gmail.com>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org
Subject: Re: [PATCH v2 0/7] bme680 cleanup
Date: Thu, 16 Aug 2018 05:55:47 -0700 [thread overview]
Message-ID: <30d5522e-3871-466b-39b5-600c37891ee4@gmail.com> (raw)
In-Reply-To: <20180816062412.GB1916@himanshu-Vostro-3559>
On 8/15/2018 11:24 PM, Himanshu Jha wrote:
> On Wed, Aug 15, 2018 at 01:38:28PM -0700, David Frey wrote:
>> Note that I don't currently have bme680 hardware available, so I am hoping that
>> Himanshu is willing to validate the changes.
>
> Another thing that is screwed up is Jonathan's email ;)
>
> It is jic23@kernel.org and not jic23@vger.kernel.org
>
> You can use:
>
> $ ./scripts/get_maintainer.pl <patch>
Yes... I realized that shortly after I received 8 bounce e-mails in reply.
prev parent reply other threads:[~2018-08-16 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 20:38 [PATCH v2 0/7] bme680 cleanup David Frey
2018-08-15 20:38 ` [PATCH v2 1/7] iio: chemical: bme680: use clamp macro David Frey
2018-08-15 20:38 ` [PATCH v2 2/7] iio: chemical: bme680: cleanup bme680_read_calib formatting David Frey
2018-08-15 20:38 ` [PATCH v2 3/7] iio: chemical: bme680: indent #defines consistently David Frey
2018-08-15 20:38 ` [PATCH v2 4/7] iio: chemical: bme680: change MSK->MASK in #defines David Frey
2018-08-15 21:03 ` David Frey
2018-08-16 6:17 ` Himanshu Jha
2018-08-15 20:38 ` [PATCH v2 5/7] iio: chemical: bme680: use GENMASK macro David Frey
2018-08-15 20:38 ` [PATCH v2 6/7] iio: chemical: bme680: use FIELD_GET macro David Frey
2018-08-15 20:38 ` [PATCH v2 7/7] iio: chemical: bme680: simplify oversampling handling David Frey
2018-08-16 6:24 ` [PATCH v2 0/7] bme680 cleanup Himanshu Jha
2018-08-16 12:55 ` David Frey [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=30d5522e-3871-466b-39b5-600c37891ee4@gmail.com \
--to=dpfrey@gmail.com \
--cc=himanshujha199640@gmail.com \
--cc=jic23@kernel.org \
--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