From: Jakub Kicinski <kuba@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Ethan Nelson-Moore <enelsonmoore@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: MAINTAINERS: Add self for the 3c509 network driver
Date: Sun, 10 May 2026 08:58:41 -0700 [thread overview]
Message-ID: <20260510085841.243bdd7e@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2605100246020.46195@angie.orcam.me.uk>
On Sun, 10 May 2026 02:57:15 +0100 (BST) Maciej W. Rozycki wrote:
> On Sat, 9 May 2026, Ethan Nelson-Moore wrote:
> > > This patch was applied to netdev/net.git (main)
> > > by Jakub Kicinski <kuba@kernel.org>:
> > > - MAINTAINERS: Add self for the 3c509 network driver
> >
> > Hi, Jakub,
> >
> > Did you forget to revert the driver removal, or have you just not gotten
> > around to it yet?
>
> Thanks for the heads-up. I can see the removal was fast-tracked to
> Linus; I didn't expect that, waiting a couple of weeks for people to speak
> out wouldn't have hurt. Now `git revert 91f3a27ae9f6' is in order.
> Shall I post the output from that, or what is the expected way to handle
> this situation?
Sorry, must have missed it or forgotten.
Could you point me to the report of these driver being used?
next prev parent reply other threads:[~2026-05-10 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 10:23 MAINTAINERS: Add self for the 3c509 network driver Maciej W. Rozycki
2026-04-27 14:36 ` Andrew Lunn
2026-05-08 22:00 ` patchwork-bot+netdevbpf
2026-05-09 23:05 ` Ethan Nelson-Moore
2026-05-10 1:57 ` Maciej W. Rozycki
2026-05-10 15:58 ` Jakub Kicinski [this message]
2026-05-10 21:44 ` Ethan Nelson-Moore
2026-05-11 23:20 ` Jakub Kicinski
2026-05-12 10:26 ` Maciej W. Rozycki
2026-05-12 15:53 ` Jakub Kicinski
2026-05-10 15:59 ` Jakub Kicinski
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=20260510085841.243bdd7e@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=enelsonmoore@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=netdev@vger.kernel.org \
/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.