From: Andrew Lunn <andrew@lunn.ch>
To: "Köry Maincent" <kory.maincent@bootlin.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>
Subject: Re: [PATCH] firmware_loader: Expand Firmware upload error codes with firmware invalid error
Date: Mon, 20 Nov 2023 17:52:09 +0100 [thread overview]
Message-ID: <4cae34b1-b68b-4ebd-aee9-4e39f4243f9f@lunn.ch> (raw)
In-Reply-To: <20231120162537.468de5b6@kmaincent-XPS-13-7390>
> 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
next prev parent reply other threads:[~2023-11-20 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 10:27 Kory Maincent
2023-11-17 13:45 ` Greg Kroah-Hartman
2023-11-17 14:06 ` Andrew Lunn
2023-11-17 19:48 ` Greg Kroah-Hartman
2023-11-20 15:25 ` Köry Maincent
2023-11-20 16:52 ` Andrew Lunn [this message]
2023-11-20 17:09 ` Conor Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4cae34b1-b68b-4ebd-aee9-4e39f4243f9f@lunn.ch \
--to=andrew@lunn.ch \
--cc=conor@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kory.maincent@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®