From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, kuba@kernel.org, davem@davemloft.net,
linux@armlinux.org.uk, hkallweit1@gmail.com, andrew@lunn.ch,
vladimir.oltean@nxp.com, f.fainelli@gmail.com
Subject: Re: [PATCH v2 net-next 0/1] mscc-miim probe cleanup
Date: Sat, 09 Apr 2022 03:40:12 +0000 [thread overview]
Message-ID: <164947561268.6004.16808779070989074436.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220407234445.114585-1-colin.foster@in-advantage.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 Apr 2022 16:44:44 -0700 you wrote:
> I'm submitting this patch independently from my ongoing patch set to
> include external control over Ocelot chips.
>
> Initially the sole patch had reviewed-by tags from Vladimir Oltean and
> Florian Fainelli, but since I had to manually resolve some conflicts I
> removed the tags.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/1] net: mdio: mscc-miim: add local dev variable to cleanup probe function
https://git.kernel.org/netdev/net-next/c/626a5aaa5067
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:[~2022-04-09 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 23:44 [PATCH v2 net-next 0/1] mscc-miim probe cleanup Colin Foster
2022-04-07 23:44 ` [PATCH v2 net-next 1/1] net: mdio: mscc-miim: add local dev variable to cleanup probe function Colin Foster
2022-04-08 12:48 ` Vladimir Oltean
2022-04-09 3: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=164947561268.6004.16808779070989074436.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=colin.foster@in-advantage.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).