On Tue, Feb 15, 2022 at 05:56:17AM +0000, Joel Stanley wrote: > On Mon, 14 Feb 2022 at 12:05, Jonathan Neuschäfer <j.neuschaefer@xxxxxxx> wrote: > > > > On Wed, Feb 02, 2022 at 02:10:44PM +0200, Andy Shevchenko wrote: > > > On Wed, Feb 2, 2022 at 2:01 PM Jonathan Neuschäfer > > > <j.neuschaefer@xxxxxxx> wrote: > > > > On Tue, Feb 01, 2022 at 11:42:11PM +0000, Joel Stanley wrote: > > > > > On Tue, 1 Feb 2022 at 13:05, Jonathan Neuschäfer <j.neuschaefer@xxxxxxx> wrote: > > > > > > ... > > > > > > > > I assume you're sending a v6 to fix some of the warnings? > > > > > > > > No, the warnings are fairly independent of this patchset, it's just that > > > > the adjacent pinctrl-npcm7xx driver started to be built by the bot, due > > > > to my Kconfig change. I'll fix them in a separate patchset. > > > > > > I guess you need to fix that first. > > > > > > Because now and then all CIs will complain to your patch and confuse people. > > > > FWIW, Linus has applied the npcm7xx fixes to for-next in the pinctrl tree, > > which means that they are not blocking this patchset anymore, AFAICS. > > I've applied the device tree changes, and I will send a pull request > for v5.18 with those. Thanks! > I assume you want Linus to merge the pinctrl bindings and driver > through his tree. Yes, that sounds alright. Jonathan
Attachment:
signature.asc
Description: PGP signature
