On Tue, Jul 29, 2025 at 10:22:30AM +0100, Pavel Begunkov wrote: > On 7/29/25 02:19, Byungchul Park wrote: > > On Mon, Jul 28, 2025 at 07:36:54PM +0100, Pavel Begunkov wrote: > > > On 7/28/25 06:27, Byungchul Park wrote: > > > > Changes from v1: > > > > 1. Rebase on linux-next. > > > > > > net-next is closed, looks like until August 11. > > > > Worth noting, this is based on linux-next, not net-next :-) > > It doesn't matter, you're still sending it to be merged into > the net tree. Please read I'm sending it to be merged into *linux-next* tree since this's about both mm and network. However, if you are not talking about a specific tree to merge but you are referring to 'Do not send *new* net-next *content* to netdev *during the period*' in the link you shared, what should I do? As for a network patch, I already tagged 'RFC net-next' as the guide: https://lore.kernel.org/all/20250728042050.24228-1-byungchul@xxxxxx/ For a patch aiming at linux-next like this, what should I do? Should I remove netdev@xxxxxxxxxxxxxxx from the reciever list? I'm not used to this case. Byungchul > > https://docs.kernel.org/process/maintainer-netdev.html > > Especially the "git-trees-and-patch-flow" section. > > -- > Pavel Begunkov
