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: 14+ 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-24 7:27 ` Mathew McBride
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.org \
--cc=3chas3@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=andriy.shevchenko@intel.com \
--cc=bridge@lists.linux.dev \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=fourier.thomas@gmail.com \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jani.nikula@intel.com \
--cc=johannes.berg@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=kees@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mchehab+huawei@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tsbogend@alpha.franken.de \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.