[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <05a229e8-b0b6-4d29-8561-70d02f6dc31b@lunn.ch>
Date: Sat, 8 Jul 2023 22:49:00 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Ross Maynard <bids.7405@...pond.com>
Cc: Dave Jones <davej@...emonkey.org.uk>,
Thorsten Leemhuis <regressions@...mhuis.info>,
Bagas Sanjaya <bagasdotme@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Linux Networking <netdev@...r.kernel.org>,
Linux USB <linux-usb@...r.kernel.org>,
Oliver Neukum <oneukum@...e.com>
Subject: Re: Fwd: 3 more broken Zaurii - SL-5600, A300, C700
> Could someone please submit the patch for me?
You are not far from it yourself.
I've not followed the history here. Did it never work, or has it
worked in the past, and then at some point broke?
If it never worked, this would be classed as new development, and so
the patch should be for net-next. If it did work, but at some point in
time it stopped working, then it is for net.
Take a read of:
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
And produce a patch based on net, or net-next.
Also read:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
Please ask questions if anything is not clear.
Andrew
Powered by blists - more mailing lists