On 23/07/2015 at 15:11:47 +0200, Linus Walleij wrote : > On Thu, Jul 23, 2015 at 12:59 PM, Octavian Purdila > <octavian.purd...@intel.com> wrote: > > On Fri, Jun 5, 2015 at 4:59 PM, Octavian Purdila > > <octavian.purd...@intel.com> wrote: > >> Since patch "i2c / ACPI: Use 0 to indicate that device does not have > >> interrupt assigned" [1], 0 is not a valid i2c client irq anymore, so > >> change all driver's checks accordingly. > >> > >> The same issue occurs when the device is instantiated via device tree > >> with no IRQ, or from the i2c sysfs interface, even before the patch > >> above. > >> > >> [1] > >> http://lkml.kernel.org/g/<1430908148-201129-3-git-send-email-mika.westerb...@linux.intel.com> > >> > >> Signed-off-by: Octavian Purdila <octavian.purd...@intel.com> > >> Reviewed-by: Mika Westerberg <mika.westerb...@linux.intel.com> > > > > Hi Jonathan, > > > > Does this look OK to you? If so, could you pleas ACK the patch so that > > Linus can pick it up in its for-next branch if/when needed? > > Me or Torvalds? > > This looks more like a Wolfram patch to me if it should not > go through IIO. >
The first cover letter had: "Linus, since the commit above was already merged in the GPIO tree, should these fixes be merged also via the GPIO tree (with ACKs from the others subsystem maintainers)?" I believe it was referring to you ;). I can take the rtc patch if you don't plan to take it. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
