From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
UNGLinuxDriver@microchip.com, davem@davemloft.net,
kuba@kernel.org, f.fainelli@gmail.com, vivien.didelot@gmail.com,
vladimir.oltean@nxp.com, andrew@lunn.ch
Subject: Re: [PATCH net v2 0/2] net: lan966x: Fixes for sleep in atomic context
Date: Wed, 26 Jan 2022 15:50:11 +0000 [thread overview]
Message-ID: <164321221148.12592.6841652619897496438.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220125114816.187124-1-horatiu.vultur@microchip.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 25 Jan 2022 12:48:14 +0100 you wrote:
> This patch series contains 2 fixes for lan966x that is sleeping in atomic
> context. The first patch fixes the injection of the frames while the second
> one fixes the updating of the MAC table.
>
> v1->v2:
> - correct the fix tag in the second patch, it was using the wrong sha.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: lan966x: Fix sleep in atomic context when injecting frames
https://git.kernel.org/netdev/net/c/b6ab149654ef
- [net,v2,2/2] net: lan966x: Fix sleep in atomic context when updating MAC table
https://git.kernel.org/netdev/net/c/77bdaf39f3c8
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-01-26 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 11:48 Horatiu Vultur
2022-01-25 11:48 ` [PATCH net v2 1/2] net: lan966x: Fix sleep in atomic context when injecting frames Horatiu Vultur
2022-01-25 11:48 ` [PATCH net v2 2/2] net: lan966x: Fix sleep in atomic context when updating MAC table Horatiu Vultur
2022-01-26 15:50 ` 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=164321221148.12592.6841652619897496438.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®