From: patchwork-bot+netdevbpf@kernel.org
To: Yue Haibing <yuehaibing@huawei.com>
Cc: vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
colin.foster@in-advantage.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: mscc: ocelot: Remove unused declarations
Date: Tue, 22 Aug 2023 18:00:24 +0000 [thread overview]
Message-ID: <169272722452.9690.3212363558579999577.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230821130218.19096-1-yuehaibing@huawei.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Aug 2023 21:02:18 +0800 you wrote:
> Commit 6c30384eb1de ("net: mscc: ocelot: register devlink ports")
> declared but never implemented ocelot_devlink_init() and
> ocelot_devlink_teardown().
> Commit 2096805497e2 ("net: mscc: ocelot: automatically detect VCAP constants")
> declared but never implemented ocelot_detect_vcap_constants().
> Commit 403ffc2c34de ("net: mscc: ocelot: add support for preemptible traffic classes")
> declared but never implemented ocelot_port_update_preemptible_tcs().
>
> [...]
Here is the summary with links:
- [net-next] net: mscc: ocelot: Remove unused declarations
https://git.kernel.org/netdev/net-next/c/49e62a0462a2
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-08-22 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 13:02 [PATCH net-next] net: mscc: ocelot: Remove unused declarations Yue Haibing
2023-08-21 13:08 ` Vladimir Oltean
2023-08-22 18:00 ` 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=169272722452.9690.3212363558579999577.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.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 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.