From: patchwork-bot+netdevbpf@kernel.org
To: Yue Haibing <yuehaibing@huawei.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: Space.h: Remove unused function declarations
Date: Fri, 04 Aug 2023 01:30:20 +0000 [thread overview]
Message-ID: <169111262075.25155.13359566243110329523.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230802130716.37308-1-yuehaibing@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Aug 2023 21:07:16 +0800 you wrote:
> Commit 5aa83a4c0a15 (" [PATCH] remove two obsolete net drivers") remove fmv18x_probe().
> And commmit 01f4685797a5 ("eth: amd: remove NI6510 support (ni65)") leave ni65_probe().
> Commit a10079c66290 ("staging: remove hp100 driver") remove hp100 driver and hp100_probe()
> declaration is not used anymore.
>
> sonic_probe() and iph5526_probe() are never implemented since the beginning of git history.
>
> [...]
Here is the summary with links:
- [net-next] net: Space.h: Remove unused function declarations
https://git.kernel.org/netdev/net-next/c/992725ff32f5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-08-04 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 13:07 [PATCH net-next] net: Space.h: Remove unused function declarations Yue Haibing
2023-08-02 16:41 ` Stephen Hemminger
2023-08-04 1:30 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 3:52 Yue Haibing
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=169111262075.25155.13359566243110329523.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuehaibing@huawei.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).