Hi Rafael, On Tue, Mar 07, 2017 at 02:23:33PM +0100, Rafael J. Wysocki wrote: > On Tue, Mar 7, 2017 at 8:49 AM, Sakari Ailus <sakari.ailus@xxxxxx> wrote: > > Hi Rafael, > > > > On Mon, Mar 06, 2017 at 04:19:14PM +0200, Sakari Ailus wrote: > >> This set contains patches written by Mika Westerberg and by myself. The > >> patchset brings support for graphs to ACPI. The functionality achieved by > >> these patches is very similar to what the Device tree provides: the port > >> and the endpoint concept are being employed. The patches make use of the > >> _DSD property and data extensions to achieve this. The fwnode interface is > >> extended by graph functionality; this way graph information originating > >> from both OF and ACPI may be accessed using the same interface, without > >> being aware of the underlying firmware interface. > > > > I've tested the patches again on ARM (OF) and x86-64 (ACPI). > > OK > > > I have V4L2 patches depending on the ACPI graph patchset that I'd like to > > have in during the same merge window. Would you either accept a pull > > request, or could I have a branch on top of v4.11-rc1 containing these > > patches only (for media tree)? > > > > The patchset "Move firmware specific code to firmware specific locations" > > depends on "Fwnode property API fixes for OF, pset". Would you prefer to > > send the bugfixes as fixes to v4.11 or just put it all to v4.12? > > I'll put it all into v4.12 if that's not a problem. That's fine for me but see below... > > Also I don't really have the time to take care of that this week due > to other work. I'll get to it next week, most likely. Ack. Would you prefer me to send a pull request, or pick up the patches --- in the latter case I'd like to request an immutable branch with these patches only on v4.11-rc1 which I could use for basing my dependent V4L2 patches that go to the media tree. Thanks. -- Kind regards, Sakari Ailus e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
