From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Pablo_Vallesp=C3=ADn_Aranguren_=3Cpablopva014=40gmail=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-parisc@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH] net: tulip: remove xircom_cb driver
Date: Thu, 06 Aug 2026 01:40:08 +0000 [thread overview]
Message-ID: <178598040839.599522.8669819859721166117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <am48DR5FC-xTY3-D@ThinkPad-P15>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 1 Aug 2026 20:33:49 +0200 you wrote:
> A possible bug was found in investigate_read_descriptor() and a fix was
> proposed. Since this is an orphan driver for hardware that is old,
> removing the driver was suggested instead. This patch removes the driver.
>
> Link: https://lore.kernel.org/netdev/2026080158-next-diligent-b4ce@gregkh
> Signed-off-by: Pablo Vallespín Aranguren <pablopva014@gmail.com>
>
> [...]
Here is the summary with links:
- net: tulip: remove xircom_cb driver
https://git.kernel.org/netdev/net-next/c/ff3a8694c2e8
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-08-06 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 18:33 [PATCH] net: tulip: remove xircom_cb driver Pablo Vallespín Aranguren
2026-08-02 7:16 ` Greg KH
2026-08-06 1:40 ` 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=178598040839.599522.8669819859721166117.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Pablo_Vallesp=C3=ADn_Aranguren_=3Cpablopva014=40gmail=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--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.