From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jiri Slaby" <jirislaby@kernel.org>, "Jan Engelhardt" <jengelh@inai.de>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"Jeff Layton" <jlayton@kernel.org>,
"Nikolay Aleksandrov" <razor@blackwall.org>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"Wang Qing" <wangqing@vivo.com>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"Eric Dumazet" <edumazet@google.com>,
"Nathan Fontenot" <nathan.fontenot@amd.com>,
"Suma Hegde" <suma.hegde@amd.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Neeraj Upadhyay" <quic_neeraju@quicinc.com>,
"Menglong Dong" <imagedong@tencent.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Xin Long" <lucien.xin@gmail.com>,
"Chen Yu" <yu.c.chen@intel.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jonathan Corbet" <corbet@lwn.net>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Jozsef Kadlecsik" <kadlec@netfilter.org>,
"Xie Yongji" <xieyongji@bytedance.com>,
"open list:NETFILTER" <coreteam@netfilter.org>,
"Roopa Prabhu" <roopa@nvidia.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Borislav Petkov" <bp@suse.de>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Pabl o Neira Ayuso" <pablo@netfilter.org>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Petr Machata" <petrm@nvidia.com>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>,
"Kees Cook" <keescook@chromium.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Yu Zhe" <yuzhe@nfschina.com>,
"William Breathitt Gray" <vilhelm.gray@gmail.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Kuniyuki Iwashima" <kuniyu@amazon.com>,
"Shakeel Butt" <shakeelb@google.com>,
"Muchun Song" <songmuchun@bytedance.com>,
"Alexandre Ghiti" <alexandre.ghiti@canonical.com>,
"Yuwei Wang" <wangyuweihx@gmail.com>,
"Juergen Gross" <jgross@suse.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Akhmat Karakotov" <hmukos@yandex-team.ru>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Netdev <netdev@vger.kernel.org>,
"David Ahern" <dsahern@kernel.org>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Florian Westphal" <fw@strlen.de>,
"open list" <linux-kernel@vger.kernel.org>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Chuck Lever" <chuck.lever@oracle.com>,
"open list:NETFILTER" <netfilter-devel@vger.kernel.org>,
"Antoine Tenart" <atenart@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Pali Rohár" <pali@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next] Remove DECnet support from kernel
Date: Mon, 09 Jan 2023 09:44:38 +0100 [thread overview]
Message-ID: <c44bd7e8-68ff-44f8-b50b-4d27b4fe29dc@app.fastmail.com> (raw)
In-Reply-To: <ad6efc07-1706-a8e2-1478-45124838a043@kernel.org>
On Mon, Jan 9, 2023, at 09:34, Jiri Slaby wrote:
> On 09. 01. 23, 9:14, Jan Engelhardt wrote:
>> On Monday 2023-01-09 08:04, Jiri Slaby wrote:
>
> Right, we used to keep providing also defines and structs in uapi
> headers of removed functionality. So that the above socket would
> compile, but fail during runtime.
>
> I am not biased to any solution. In fact, I found out trinity was fixed
> already. So either path networking takes, it's fine by me. I'm not sure
> about the chromium users, though (and I don't care).
Chromium and some of the others look like automatically generated
lists of files and the rest seem to have compile-time checks.
From a brief look at all the packages in the debian codesearch
link you provided, I don't see any that are likely to cause
problems aside from trinity.
Arnd
prev parent reply other threads:[~2023-01-09 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 0:43 [PATCH net-next] Remove DECnet support from kernel Stephen Hemminger
2022-08-18 7:09 ` Nikolay Aleksandrov
2022-08-22 14:00 ` patchwork-bot+netdevbpf
2023-01-09 7:04 ` Jiri Slaby
2023-01-09 8:14 ` Jan Engelhardt
2023-01-09 8:34 ` Jiri Slaby
2023-01-09 8:44 ` Arnd Bergmann [this message]
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=c44bd7e8-68ff-44f8-b50b-4d27b4fe29dc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=alexandre.ghiti@canonical.com \
--cc=atenart@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=bp@suse.de \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=coreteam@netfilter.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=fw@strlen.de \
--cc=hdegoede@redhat.com \
--cc=hmukos@yandex-team.ru \
--cc=imagedong@tencent.com \
--cc=jengelh@inai.de \
--cc=jgross@suse.com \
--cc=jirislaby@kernel.org \
--cc=jlayton@kernel.org \
--cc=kadlec@netfilter.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lucien.xin@gmail.com \
--cc=martin.petersen@oracle.com \
--cc=nathan.fontenot@amd.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=pali@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@kernel.org \
--cc=petrm@nvidia.com \
--cc=quic_neeraju@quicinc.com \
--cc=razor@blackwall.org \
--cc=rdunlap@infradead.org \
--cc=roopa@nvidia.com \
--cc=sgarzare@redhat.com \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.com \
--cc=stephen@networkplumber.org \
--cc=suma.hegde@amd.com \
--cc=tsbogend@alpha.franken.de \
--cc=vilhelm.gray@gmail.com \
--cc=wangqing@vivo.com \
--cc=wangyuweihx@gmail.com \
--cc=xieyongji@bytedance.com \
--cc=yu.c.chen@intel.com \
--cc=yuzhe@nfschina.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).