From: patchwork-bot+netdevbpf@kernel.org
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
kgraul@linux.ibm.com
Subject: Re: [PATCH net 0/3] s390/qeth: fixes 2021-01-07
Date: Fri, 08 Jan 2021 03:00:08 +0000 [thread overview]
Message-ID: <161007480886.26739.12705141595571763670.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210107172442.1737-1-jwi@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Thu, 7 Jan 2021 18:24:39 +0100 you wrote:
> Hi Dave & Jakub,
>
> please apply the following patch series to netdev's net tree.
>
> This brings two locking fixes for the device control path.
> Also one fix for a path where our .ndo_features_check() attempts to
> access a non-existent L2 header.
>
> [...]
Here is the summary with links:
- [net,1/3] s390/qeth: fix deadlock during recovery
https://git.kernel.org/netdev/net/c/0b9902c1fcc5
- [net,2/3] s390/qeth: fix locking for discipline setup / removal
https://git.kernel.org/netdev/net/c/b41b554c1ee7
- [net,3/3] s390/qeth: fix L2 header access in qeth_l3_osa_features_check()
https://git.kernel.org/netdev/net/c/f9c4845385c8
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-01-08 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 17:24 [PATCH net 0/3] s390/qeth: fixes 2021-01-07 Julian Wiedmann
2021-01-07 17:24 ` [PATCH net 1/3] s390/qeth: fix deadlock during recovery Julian Wiedmann
2021-01-07 17:24 ` [PATCH net 2/3] s390/qeth: fix locking for discipline setup / removal Julian Wiedmann
2021-01-07 17:24 ` [PATCH net 3/3] s390/qeth: fix L2 header access in qeth_l3_osa_features_check() Julian Wiedmann
2021-01-08 3: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=161007480886.26739.12705141595571763670.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).