[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaxB1APxK_rRFEhcwBw0JZc20YN0z_881_iYVxeKs95LQ@mail.gmail.com>
Date: Thu, 7 Nov 2024 14:59:25 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Networking <netdev@...r.kernel.org>,
Drew Fustini <dfustini@...storrent.com>,
Emil Renner Berthing <emil.renner.berthing@...onical.com>, Jisheng Zhang <jszhang@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the pinctrl tree with the net-next tree
On Thu, Nov 7, 2024 at 11:43 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Today's linux-next merge of the pinctrl tree got a conflict in:
>
> MAINTAINERS
Thanks Stephen, looks trivial enough but will try to remember to mention
this to Torvalds.
Yours,
Linus Walleij
Powered by blists - more mailing lists