From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, vivien.didelot@gmail.com, f.fainelli@gmail.com,
davem@davemloft.net, kuba@kernel.org, linux@armlinux.org.uk
Subject: Re: [PATCH v2 net-next] net: ocelot: fix missed include in the vsc7514_regs.h file
Date: Sat, 11 Dec 2021 04:40:09 +0000 [thread overview]
Message-ID: <163919760979.24757.10249852929237407652.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211209074010.1813010-1-colin.foster@in-advantage.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Dec 2021 23:40:10 -0800 you wrote:
> commit 32ecd22ba60b ("net: mscc: ocelot: split register definitions to a
> separate file") left out an include for <soc/mscc/ocelot_vcap.h>. It was
> missed because the only consumer was ocelot_vsc7514.h, which already
> included ocelot_vcap.
>
> Fixes: 32ecd22ba60b ("net: mscc: ocelot: split register definitions to a separate file")
> Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
>
> [...]
Here is the summary with links:
- [v2,net-next] net: ocelot: fix missed include in the vsc7514_regs.h file
https://git.kernel.org/netdev/net-next/c/840ece19e9f2
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:[~2021-12-11 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 7:40 [PATCH v2 net-next] net: ocelot: fix missed include in the vsc7514_regs.h file Colin Foster
2021-12-09 17:02 ` Florian Fainelli
2021-12-11 4: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=163919760979.24757.10249852929237407652.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).