On 2017-05-29 14:39, Linus Walleij wrote: > On Fri, May 26, 2017 at 6:02 PM, Jan Kiszka <jan.kiszka@xxxxxxxxxxx> wrote: > >> This makes the gpio-exar driver usable, which was prevented by a number >> of fatal bugs, and adds support for the SIMATIC IOT2040 to the 8250-exar >> driver and, indirectly, to gpio-exar as well. It's a cross-subsystem >> series, so I'm also cross-posting to the serial and gpio lists. >> >> Changes in v3: >> - fix MPIO state for Commtech adapters (regression of merged patch from >> previous round) >> - do not create gpio device for Commtech adapters >> - switch back to device properties >> - pass parent reference via device.parent instead of platform data >> - use dmi_system_id table instead of open-coded matching >> - address some smaller review remarks >> - fix reading back of rs485 state >> - adjust parenthood of exar gpiochip > > I ACKed some patches if Greg need to merge them. Thanks! > > Can you suggest a merge strategy for this patch set? > > It appears Greg will have to merge at least the first one. > > Will it work to merge the GPIO patches orthogonally to the GPIO > tree or are they all dependent on the serial changes? > > Should I merge them all? Should Greg merge them all? > Should one of us produce an immutable branch? Half of the patch are affecting both serial and GPIO subsystem, most have GPIO focus, though. Just patch 10 or more serial than GPIO. All in all, maybe Greg can ack and things can flow through the GPIO tree? Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
