[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM5PR1001MB09945AA014D512511E4DF4A880500@AM5PR1001MB0994.EURPRD10.PROD.OUTLOOK.COM>
Date: Tue, 17 Dec 2019 09:55:38 +0000
From: Adam Thomson <Adam.Thomson.Opensource@...semi.com>
To: Marco Felsch <m.felsch@...gutronix.de>,
Linus Walleij <linus.walleij@...aro.org>
CC: Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
Support Opensource <Support.Opensource@...semi.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: RE: [RESEND PATCH v3 3/3] pinctrl: da9062: add driver support
On 17 December 2019 06:40, Marco Felsch wrote:
> On 19-12-16 11:33, Linus Walleij wrote:
> > On Mon, Dec 16, 2019 at 8:47 AM Marco Felsch <m.felsch@...gutronix.de>
> wrote:
> >
> > > Nice catch, Linus is it okay to add this as follow up patch? The current
> > > patch isn't wrong without the 'PIN_CONFIG_BIAS_DISABLE' case.
> >
> > No strong opinion on that as long as the result is running code.
>
> Of course the code is running and was tested. Just didn't covered this
> use case.
>
> Adam is this okay with you?
If you want to send a follow up straight after then that's ok although to me
that seems like more effort. :)
Anyway:
Reviewed-by: Adam Thomson <Adam.Thomson.Opensource@...semi.com>
>
> Regards,
> Marco
>
> > Yours,
> > Linus Walleij
> >
Powered by blists - more mailing lists