On Thu, 2017-01-12 at 13:51 +0100, Alexander Stein wrote: > On Thursday 12 January 2017 14:15:12, Andy Shevchenko wrote: > > On Thu, 2017-01-12 at 08:27 +0100, Alexander Stein wrote: > > > On Wednesday 11 January 2017 16:14:57, Andy Shevchenko wrote: > > > > On Wed, 2017-01-11 at 15:35 +0200, Andy Shevchenko wrote: > > > > > On Wed, 2017-01-11 at 13:21 +0100, Linus Walleij wrote: > > > > > > On Mon, Jan 9, 2017 at 3:02 PM, Andy Shevchenko > > > > > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > > Alas, it doesn't apply clearly. gpio_keys_polled.c has been > > > > changed > > > > a > > > > lot from that time. So, would you like to fix it yourself? > > > > > > > > Since mine is applied clearly I may do other way around, rebase > > > > and > > > > fix > > > > that patch on top of mine. > > > > How does it sound? > > > Yeah, I noticed that gpio_keys_polled.c has changed meanwhile, so > > > my > > > patch has > > > to be modifed anyway. If your patch is applied somewhere I can > > > rebase > > > my > > > change on that and resubmit. > > First of all, how do you feel if Linus applies my change first? > I don't mind. Just go ahead and point me somewhere I can base on. For now the only my topic/uart/rpm branch [1] on bitbucket contains it. (It also has many other patches, meaning you need to base your branch on top of gpio-next + cherry-picked the only one from my branch) [1] https://bitbucket.org/andy-shev/linux/branch/topic%2Fuart%2frpm -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- 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