Hello Dmitry, On Thu, Feb 04, 2016 at 01:18:42PM -0800, Dmitry Torokhov wrote: > On Wed, Feb 03, 2016 at 10:35:27AM +0100, Uwe Kleine-König wrote: > > Hello, > > > > On Tue, Feb 02, 2016 at 01:10:19PM +0100, Daniel Mack wrote: > > > On 02/02/2016 11:24 AM, Uwe Kleine-König wrote: > > > > This is a preparation for the next patche. There is no change in > > > > behaviour intended. > > > > > > This one looks good to me, but it clashes with Dmitry's latest patch > > > sets (which I haven't found the time to test yet, sorry!). > > > > There is nothing in next-20160203, so I assume Dmitry either fixes this > > up when applying my patches or tells me when I should rebase. > > Please take a look at my rotary-encoder branch. I am waiting to merge it > into next until I can get some testers. If you have raumfild device that > would be awesome. I don't have a raumfeld device. I did a similar conversion and the only relevant difference is that I used .dev_id = "rotary_encoder.0", while you used .dev_id = "rotary-encoder", in raumfeld_rotary_gpios_table. I think a mixture of these is the right thing, i.e. .dev_id = "rotary-encoder.0", Your series obsoletes my first two patches, so I will port my third patch on top of your branch and retest there. 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 devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
