All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Lukas Bulwahn <lbulwahn@redhat.com>,
	Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: remove obsolete file entry in NETWORKING DRIVERS
Date: Fri, 23 Jan 2026 19:45:59 +0000	[thread overview]
Message-ID: <aXPP9_z3Iu9l4C4G@horms.kernel.org> (raw)
In-Reply-To: <20260123101807.27beafe7@kernel.org>

On Fri, Jan 23, 2026 at 10:18:07AM -0800, Jakub Kicinski wrote:
> On Fri, 23 Jan 2026 17:15:19 +0000 Simon Horman wrote:
> > On Thu, Jan 22, 2026 at 08:46:09AM +0100, Lukas Bulwahn wrote:
> > > From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
> > > 
> > > Commit d8f87aa5fa0a ("net: remove HIPPI support and RoadRunner HIPPI
> > > driver") removes the hippidevice header file, but misses that there is
> > > still a file entry in MAINTAINERS referring to it.
> > > 
> > > Remove the obsolete file entry in NETWORKING DRIVERS.
> > > 
> > > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>  
> > 
> > Thanks Lukas,
> > 
> > I agree this is the case.
> > 
> > But unfortunately our CI seems to be confused about which
> > tree to test it against. So could you resubmit targeting net-next
> > like this?
> 
> It's alright, we don't really have any tests for MAINTAINERS in the CI,
> anyway.

Yes, silly me.

  reply	other threads:[~2026-01-23 19:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22  7:46 [PATCH] MAINTAINERS: remove obsolete file entry in NETWORKING DRIVERS Lukas Bulwahn
2026-01-23 17:15 ` Simon Horman
2026-01-23 18:18   ` Jakub Kicinski
2026-01-23 19:45     ` Simon Horman [this message]
2026-01-23 18:50 ` patchwork-bot+netdevbpf
  -- strict thread matches above, loose matches on Subject: below --
2026-05-19  9:16 Lukas Bulwahn
2026-05-19  9:33 ` Arnd Bergmann
2026-05-21  2:10 ` 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=aXPP9_z3Iu9l4C4G@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=lbulwahn@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.