From: patchwork-bot+netdevbpf@kernel.org
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: netdev@vger.kernel.org, linux-mips@vger.kernel.org,
linux-pci@vger.kernel.org, rust-for-linux@vger.kernel.org,
jes@trained-monkey.org, tsbogend@alpha.franken.de,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bhelgaas@google.com,
horms@kernel.org, dakr@kernel.org, kwilczynski@kernel.org,
ojeda@kernel.org, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
akpm@linux-foundation.org, martink@posteo.de, pavel@ucw.cz,
johan.korsnes@gmail.com, geert@linux-m68k.org,
paul@paul-moore.com, tytso@mit.edu, kuniyu@google.com,
ebiggers@google.com, tglx@linutronix.de, mingo@kernel.org,
linux@treblig.org
Subject: Re: [PATCH net-next] net: remove HIPPI support and RoadRunner HIPPI driver
Date: Wed, 21 Jan 2026 03:20:05 +0000 [thread overview]
Message-ID: <176896560511.710718.2129233075354584657.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260119022451.22344-1-enelsonmoore@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 18 Jan 2026 18:24:04 -0800 you wrote:
> HIPPI has not been relevant for over two decades. It was rapidly
> eclipsed by Fibre Channel, and even when it was new, it was
> confined to very high-end hardware. The HIPPI code has only
> received tree-wide changes and fixes by inspection in the entire
> Git history. Remove HIPPI support and the rrunner HIPPI driver,
> and move the former maintainer to the CREDITS file. Keep the
> include/uapi/linux/if_hippi.h header because it is used by the TUN
> code, and to avoid breaking userspace, however unlikely that may be.
>
> [...]
Here is the summary with links:
- [net-next] net: remove HIPPI support and RoadRunner HIPPI driver
https://git.kernel.org/netdev/net-next/c/d8f87aa5fa0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-21 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 2:24 [PATCH net-next] net: remove HIPPI support and RoadRunner HIPPI driver Ethan Nelson-Moore
2026-01-21 3:20 ` patchwork-bot+netdevbpf [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=176896560511.710718.2129233075354584657.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=gary@garyguo.net \
--cc=geert@linux-m68k.org \
--cc=horms@kernel.org \
--cc=jes@trained-monkey.org \
--cc=johan.korsnes@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@treblig.org \
--cc=lossin@kernel.org \
--cc=martink@posteo.de \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=pavel@ucw.cz \
--cc=rust-for-linux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tmgross@umich.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox