[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdasoyFVrRzgL+M7LSMCY+oE5+1kBWnwZr17vgrzdA4jQg@mail.gmail.com>
Date: Thu, 23 Jul 2015 15:31:41 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Octavian Purdila <octavian.purdila@...el.com>
Cc: Jonathan Cameron <jic23@...nel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald <pmeerw@...erw.net>,
Alessandro Zummo <a.zummo@...ertech.it>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] iio: fix drivers that consider 0 as a valid IRQ in client->irq
On Thu, Jul 23, 2015 at 3:23 PM, Octavian Purdila
<octavian.purdila@...el.com> wrote:
> On Thu, Jul 23, 2015 at 4:11 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
>> Me or Torvalds?
>>
>> This looks more like a Wolfram patch to me if it should not
>> go through IIO.
>>
>
> Hi Linus,
>
> This patch fixes one issue introduced by "i2c / ACPI: Use 0 to
> indicate that device does not have interrupt assigned" which I see it
> is merged in the GPIO for-next branch. That is why I thought you will
> pick it up, did I assume wrong?
Aha yeah O already forgot that I merged that.
That patch is not in -next, it is already in Torvalds'
tree.
So fixes can be merged directly through the IIO tree
without any GPIO dependencies.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists