Hello Linus, On Mon, Jul 20, 2015 at 09:41:09AM +0200, Linus Walleij wrote: > On Mon, Jul 20, 2015 at 8:56 AM, Uwe Kleine-König > <u.kleine-koenig@xxxxxxxxxxxxxx> wrote: > > Hello Linus, > > > > On Fri, Jul 17, 2015 at 02:28:25PM +0200, Linus Walleij wrote: > >> On Wed, Jul 15, 2015 at 8:39 AM, Alexandre Courbot <gnurou@xxxxxxxxx> wrote: > >> > I'm all for taking this into -next ASAP then. Linus has control over > >> > the tree though, so his action is required. > >> > >> I am pushing it today. > >> > >> I finally found this message in my messy inbox. I'm a bit up over my > >> ears in patches... > > This somehow failed. My tag is merged in your devel branch, but this > > contains several commits missing in your for-next. Is this intended? > > No ... :( > > I just pulled it in. If anything is to blame, I hope it's not me, I just > issued git pull. > > commit 2563606ce45314bfeae811edfa9984b1921fff06 > Merge: 015403145a65 b17d1bf16cc7 > Author: Linus Walleij <linus.walleij@xxxxxxxxxx> > Date: Fri Jul 17 13:44:15 2015 +0200 > > Merge tag 'gpiod-flags-for-4.3' of > git://git.pengutronix.de/git/ukl/linux into devel > > The last patch in this series makes the flags parameter for the various > gpiod_get* functions mandatory and so allows to remove an ugly cpp hack > introduced in commit 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() > functions) for v3.17-rc1. > > The other nine commits fix the last remaining users of these functions that > don't pass flags yet. (Only etraxfs-uart wasn't fixed; this > driver's use of the > gpiod functions needs fixing anyhow.) this is fine. It contains my signed data (you have to do git cat-file commit 2563606ce45314bfeae811edfa9984b1921fff06 to see that) and the usual ö-Problem doesn't exist here, because it was me who created the commits. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html