[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cae34b1-b68b-4ebd-aee9-4e39f4243f9f@lunn.ch>
Date: Mon, 20 Nov 2023 17:52:09 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Köry Maincent <kory.maincent@...tlin.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Luis Chamberlain <mcgrof@...nel.org>,
Russ Weight <russ.weight@...ux.dev>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
linux-kernel@...r.kernel.org, Conor Dooley <conor@...nel.org>
Subject: Re: [PATCH] firmware_loader: Expand Firmware upload error codes with
firmware invalid error
> Sorry, my fault, I did not know well the merge actions that were needed for
> this particular case.
>
> > > If you don't want to do that, we can ask Arnd to take it, and he can
> > > create a stable branch which we pull into netdev.
> >
> > You want a stable tag to pull from, right?
> >
> > But really, why not just take this through netdev? It's just one
> > commit, I have no problem with it going that way at all. If the odd
> > chance there's a merge conflict in the future, I can handle it.
>
> Seems a good and simple idea to me, Andrew any thoughts about it?
> Do I send a single patch to net-next and ask Conor to pull it in his
> subsystem for his patch series?
Yes, send a single patch to netdev. Under the ---, ask for a stable
branch. Jakub should then hopefully reply with information about the
branch, which other Maintainers can then pull.
Andrew
Powered by blists - more mailing lists