From: Jonathan Cameron <jic23@kernel.org>
To: Bastien Nocera <hadess@hadess.net>,
Octavian Purdila <octavian.purdila@intel.com>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net
Cc: srinivas.pandruvada@linux.intel.com, daniel.baluta@intel.com,
irina.tirdea@intel.com, ao2@ao2.it,
u.kleine-koenig@pengutronix.de, vlad.dogaru@intel.com,
linus.walleij@linaro.org, tiberiu.a.breana@intel.com,
javier@osg.samsung.com, dan.carpenter@oracle.com,
geert@linux-m68k.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: remove gpio interrupt probing from drivers that use a single interrupt
Date: Sat, 3 Oct 2015 11:07:21 +0100 [thread overview]
Message-ID: <560FA8D9.9060104@kernel.org> (raw)
In-Reply-To: <1442999087.3658.22.camel@hadess.net>
On 23/09/15 10:04, Bastien Nocera wrote:
> On Wed, 2015-09-23 at 12:02 +0300, Octavian Purdila wrote:
>> Commit 845c877009cf014b ("i2c / ACPI: Assign IRQ for devices that
>> have
>> GpioInt automatically") automatically asigns
>
> assigns.
Fixed up description and applied to the togreg branch of iio.git.
Initially pushed out as testing. Nice to finally clear this lot
out! Now I just have to remember that we don't need this boiler
plate ever again.
Thanks,
Jonathan
>
>> the first ACPI GPIO
>> interrupt in client->irq, so we can remove the probing code from
>> drivers that use only one interrupt.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2015-10-03 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:01 [PATCH 0/2] remove unused ACPI GPIO interrupt probing code Octavian Purdila
2015-09-23 9:02 ` [PATCH 1/2] iio: fix drivers that use 0 as a valid IRQ in client->irq (part 2) Octavian Purdila
2015-10-03 10:07 ` Jonathan Cameron
2015-09-23 9:02 ` [PATCH 2/2] iio: remove gpio interrupt probing from drivers that use a single interrupt Octavian Purdila
2015-09-23 9:04 ` Bastien Nocera
2015-10-03 10:07 ` Jonathan Cameron [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=560FA8D9.9060104@kernel.org \
--to=jic23@kernel.org \
--cc=ao2@ao2.it \
--cc=dan.carpenter@oracle.com \
--cc=daniel.baluta@intel.com \
--cc=geert@linux-m68k.org \
--cc=hadess@hadess.net \
--cc=irina.tirdea@intel.com \
--cc=javier@osg.samsung.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=octavian.purdila@intel.com \
--cc=pmeerw@pmeerw.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tiberiu.a.breana@intel.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vlad.dogaru@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;
as well as URLs for NNTP newsgroup(s).