From: Jakub Kicinski <kuba@kernel•org>
To: Andy Shevchenko <andriy.shevchenko@intel•com>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, andrew+netdev@lunn•ch, horms@kernel•org,
corbet@lwn•net, skhan@linuxfoundation•org, linux@armlinux•org.uk,
tsbogend@alpha•franken.de, maddy@linux•ibm.com,
mpe@ellerman•id.au, npiggin@gmail•com, chleroy@kernel•org,
3chas3@gmail•com, razor@blackwall•org, idosch@nvidia•com,
jani.nikula@intel•com, mchehab+huawei@kernel•org, tytso@mit•edu,
herbert@gondor•apana.org.au, geert@linux-m68k•org,
ebiggers@kernel•org, johannes.berg@intel•com,
jonathan.cameron@huawei•com, kees@kernel•org, kuniyu@google•com,
fourier.thomas@gmail•com, rdunlap@infradead•org,
akpm@linux-foundation•org, linux-doc@vger•kernel.org,
linux-mips@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
bridge@lists•linux.dev, dwmw2@infradead•org
Subject: Re: [PATCH net-deletions v2] net: remove unused ATM protocols and legacy ATM device drivers
Date: Thu, 23 Apr 2026 12:22:27 -0700 [thread overview]
Message-ID: <20260423122227.1454f68c@kernel.org> (raw)
In-Reply-To: <aeh0CV3UQw1quCXv@ashevche-desk.local>
On Wed, 22 Apr 2026 10:08:57 +0300 Andy Shevchenko wrote:
> Since it's almost removal and it will go via netdev tree (same tree you are
> maintaining, I suppose) the -D would have a big help to review the changes
> (and not see removals at all, as 32k lines of one email is too much).
Good point, I'll remember for the future deletions
next prev parent reply other threads:[~2026-04-23 19:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 4:18 [PATCH net-deletions v2] net: remove unused ATM protocols and legacy ATM device drivers Jakub Kicinski
2026-04-22 7:08 ` Andy Shevchenko
2026-04-23 14:54 ` Paolo Abeni
2026-04-23 19:22 ` Jakub Kicinski [this message]
2026-04-22 10:53 ` Simon Horman
2026-04-22 13:05 ` David Woodhouse
2026-04-23 2:38 ` Jakub Kicinski
2026-04-23 2:41 ` Philip Prindeville
2026-04-23 7:53 ` Andy Shevchenko
2026-04-23 11:36 ` David Woodhouse
2026-04-22 13:17 ` Nikolay Aleksandrov
2026-04-25 10:16 ` Maciej W. Rozycki
2026-04-27 0:36 ` patchwork-bot+netdevbpf
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=20260423122227.1454f68c@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=3chas3@gmail$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=andriy.shevchenko@intel$(echo .)com \
--cc=bridge@lists$(echo .)linux.dev \
--cc=chleroy@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=dwmw2@infradead$(echo .)org \
--cc=ebiggers@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=fourier.thomas@gmail$(echo .)com \
--cc=geert@linux-m68k$(echo .)org \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=horms@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=jani.nikula@intel$(echo .)com \
--cc=johannes.berg@intel$(echo .)com \
--cc=jonathan.cameron@huawei$(echo .)com \
--cc=kees@kernel$(echo .)org \
--cc=kuniyu@google$(echo .)com \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-mips@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=maddy@linux$(echo .)ibm.com \
--cc=mchehab+huawei@kernel$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=netdev@vger$(echo .)kernel.org \
--cc=npiggin@gmail$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=razor@blackwall$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
--cc=tsbogend@alpha$(echo .)franken.de \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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