From: patchwork-bot+netdevbpf@kernel.org
To: Lijun Pan <ljp@linux.ibm.com>
Cc: netdev@vger.kernel.org, sukadev@linux.ibm.com, drt@linux.ibm.com
Subject: Re: [PATCH net v2 0/3] ibmvnic: null pointer dereference
Date: Wed, 25 Nov 2020 00:40:05 +0000 [thread overview]
Message-ID: <160626480590.25353.12237678107052938005.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201123193547.57225-1-ljp@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Mon, 23 Nov 2020 13:35:44 -0600 you wrote:
> Fix two NULL pointer dereference crash issues.
> Improve module removal procedure.
>
> In v2, we split v1 into 3 sets according to patch dependencies so that
> individual author can rework on them during the coming holiday.
> 1-11 as a set since they are dependent and most of them are Dany's.
> 12-14 as a set since they are independent of 1-11.
> 15 to be sent to net-next.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] ibmvnic: fix NULL pointer dereference in reset_sub_crq_queues
https://git.kernel.org/netdev/net/c/a0faaa27c716
- [net,v2,2/3] ibmvnic: fix NULL pointer dereference in ibmvic_reset_crq
https://git.kernel.org/netdev/net/c/0e435befaea4
- [net,v2,3/3] ibmvnic: enhance resetting status check during module exit
https://git.kernel.org/netdev/net/c/3ada288150fb
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:[~2020-11-25 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 19:35 [PATCH net v2 0/3] ibmvnic: null pointer dereference Lijun Pan
2020-11-23 19:35 ` [PATCH net v2 1/3] ibmvnic: fix NULL pointer dereference in reset_sub_crq_queues Lijun Pan
2020-11-23 19:35 ` [PATCH net v2 2/3] ibmvnic: fix NULL pointer dereference in ibmvic_reset_crq Lijun Pan
2020-11-23 19:35 ` [PATCH net v2 3/3] ibmvnic: enhance resetting status check during module exit Lijun Pan
2020-11-25 0: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=160626480590.25353.12237678107052938005.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=drt@linux.ibm.com \
--cc=ljp@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sukadev@linux.ibm.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).