From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Breana, Tiberiu A" <tiberiu.a.breana@intel.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>
Subject: Re: [patch] iio: humidity: Remove a stray unlock
Date: Tue, 17 May 2016 08:00:51 +0000 [thread overview]
Message-ID: <20160517080051.GB11011@mwanda> (raw)
In-Reply-To: <4586F61A4A291F4DA44D32824E7C0F4023597A48@IRSMSX109.ger.corp.intel.com>
On Tue, May 17, 2016 at 07:43:21AM +0000, Breana, Tiberiu A wrote:
> That one must have slipped by during development versions.
> You might also want to add am2315 in the patch title.
Yeah. I'll resend.
I obviously just mindlessly cut and pasted that from the earlier patch:
Fixes: 0d96d5ead3f7 ('iio: humidity: Add triggered buffer support for AM2315')
That patch also has the wrong subject line because it was just copied
from the first patch 366a3270c1c5 ('iio: humidity: Add support for
AM2315').
And just a few minutes ago I was giving another new driver its own
prefix. But even though I thought--more than I should have--about
what the author wanted to use as a prefix for his driver, I still
probably read his mind incorrectly.
In other words, we need to start with the correct prefix from square
one: iio: humidity: am2315: Add support for AM2315
regards,
dan carpenter
next prev parent reply other threads:[~2016-05-17 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 7:31 [patch] iio: humidity: Remove a stray unlock Dan Carpenter
2016-05-17 7:43 ` Breana, Tiberiu A
2016-05-17 8:00 ` Dan Carpenter [this message]
2016-05-17 8:02 ` [patch v2] iio: humidity: am2315: " Dan Carpenter
2016-05-21 16:48 ` 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=20160517080051.GB11011@mwanda \
--to=dan.carpenter@oracle.com \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=tiberiu.a.breana@intel.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