On Thu, 20 Jul 2017, Andrey Smirnov wrote: > On Thu, Jul 20, 2017 at 2:04 AM, Lee Jones <lee.jones@xxxxxxxxxx> wrote: > > Where is patch 1? > > > > lkml.kernel.org/r/20170718175604.11735-2-andrew.smirnov@xxxxxxxxx > > I dropped you from CC list to spare you the e-mail traffic, but I can > add you back if you'd prefer that. It's always handy to see the C code which handles these bindings. Also, it looks like there is an MFD change in that patch, so I should have been Cc'ed anyway. > >> Cc: cphealy@xxxxxxxxx > >> Cc: Lucas Stach <l.stach@xxxxxxxxxxxxxx> > >> Cc: Nikita Yushchenko <nikita.yoush@xxxxxxxxxxxxxxxxxx> > >> Cc: Rob Herring <robh+dt@xxxxxxxxxx> > >> Cc: Mark Rutland <mark.rutland@xxxxxxx> > >> Cc: devicetree@xxxxxxxxxxxxxxx > >> Acked-by: Rob Herring <robh@xxxxxxxxxx> > >> Signed-off-by: Andrey Smirnov <andrew.smirnov@xxxxxxxxx> > >> --- > >> .../devicetree/bindings/mfd/zii,rave-sp.txt | 39 ++++++++++++++++++++++ > >> 1 file changed, 39 insertions(+) > >> create mode 100644 Documentation/devicetree/bindings/mfd/zii,rave-sp.txt > >> > >> diff --git a/Documentation/devicetree/bindings/mfd/zii,rave-sp.txt b/Documentation/devicetree/bindings/mfd/zii,rave-sp.txt > >> new file mode 100644 > >> index 000000000000..61d9105ded07 > >> --- /dev/null > >> +++ b/Documentation/devicetree/bindings/mfd/zii,rave-sp.txt > >> @@ -0,0 +1,39 @@ > >> +Zodiac Inflight Innovations RAVE Supervisory Processor > >> + > >> +RAVE Supervisory Processor communicates with SoC over UART. It is > >> +expected that its device-tree node is specified as a child of a node > > > > Nit: Device Tree > > > > Once fixed, please apply my: > > > > For my own reference: > > Acked-for-MFD-by: Lee Jones <lee.jones@xxxxxxxxxx> > > > > OK. Will do. > > Thanks, > Andrey Smirnov -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- 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
