From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, stable@vger.kernel.org,
tsbogend@alpha.franken.de, mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, lukas.bulwahn@gmail.com,
stephen@networkplumber.org, leon@kernel.org, geoff@infradead.org,
petrm@nvidia.com, wsa+renesas@sang-engineering.com,
linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH net] eth: fealnx: bring back this old driver
Date: Thu, 09 Mar 2023 07:30:19 +0000 [thread overview]
Message-ID: <167834701946.22182.5252646764368734052.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230307171930.4008454-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Mar 2023 09:19:30 -0800 you wrote:
> This reverts commit d5e2d038dbece821f1af57acbeded3aa9a1832c1.
>
> We have a report of this chip being used on a
>
> SURECOM EP-320X-S 100/10M Ethernet PCI Adapter
>
> which could still have been purchased in some parts
> of the world 3 years ago.
>
> [...]
Here is the summary with links:
- [net] eth: fealnx: bring back this old driver
https://git.kernel.org/netdev/net/c/8f1482080104
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:[~2023-03-09 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:19 [PATCH net] eth: fealnx: bring back this old driver Jakub Kicinski
2023-03-09 7:30 ` 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=167834701946.22182.5252646764368734052.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geoff@infradead.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=tsbogend@alpha.franken.de \
--cc=wsa+renesas@sang-engineering.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).