Messages in this thread | | | Date | Mon, 20 Nov 2023 16:25:37 +0100 | From | Köry Maincent <> | Subject | Re: [PATCH] firmware_loader: Expand Firmware upload error codes with firmware invalid error |
| |
On Fri, 17 Nov 2023 14:48:32 -0500 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > > > This patch was initially submitted as part of a net patch series. > > > > Conor expressed interest in using it in a different subsystem. > > > > Consequently, I extracted it from the series and submitted it separately > > > > to the main tree, driver-core. > > > > https://lore.kernel.org/netdev/20231116-feature_poe-v1-7-be48044bf249@bootlin.com/ > > > > > > > > > > So you want me to take it through my tree? Sure, but if you are relying > > > on this for any other code, it will be a while before it gets into > > > Linus's tree, not until 6.8-rc1, is that ok? > > > > My idea was that you could create a stable branch, which can then be > > pulled into netdev and arm-soc. > > I'll be glad to do so, you just need to ask me to do that, I don't see > that request here :)
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?
Regards, -- Köry Maincent, Bootlin Embedded Linux and kernel engineering https://bootlin.com
| |