Re: [PATCH net-next 0/2] appletalk: move the protocol out of tree
Andrew Lunn <[email protected]>
| Newsgroups | org.kernel.vger.linux-m68k,org.kernel.vger.linux-mips,org.kernel.vger.netdev,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jun 18, 2026 at 10:13:08AM +0200, Geert Uytterhoeven wrote: > Hi Andrew, > > On Thu, 18 Jun 2026 at 10:01, Andrew Lunn <[email protected]> wrote: > > If the appletalk community can take the workload off the top level > > maintainers, respond to all patches within 2 to 3 days, give > > Reviewed-by, or make change requests, it can probably stay in the > > Mainline kernel. Otherwise it will move out of tree. > > "2 or 3 days" is rather short. If we would have to move all code > maintained by people who cannot respond to all patches within 2 to > 3 days out of the mainline kernel, you'd end up with a networking > subsystem without supporting OS ;-) I do agree that every subsystem is different, but that is the speed netdev goes, often faster. There are around 150 patches a day submitted, and in order to not drown in those patches, they need to be processed fast. It is however known for a sub-subsystem to move out of netdev to a mailing list and a git tree of its own, and just send git pull requests to netdev. It can then move at its own speed. Andrew