netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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,
	brking@linux.vnet.ibm.com, dnbanerg@us.ibm.com,
	tlfalcon@linux.ibm.com
Subject: Re: [PATCH net-next v2 0/2] rework the memory barrier for SCRQ entry
Date: Tue, 02 Feb 2021 04:30:07 +0000	[thread overview]
Message-ID: <161224020794.9509.11960411803239623836.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210130011905.1485-1-ljp@linux.ibm.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri, 29 Jan 2021 19:19:03 -0600 you wrote:
> This series rework the memory barrier for SCRQ (Sub-Command-Response
> Queue) entry.
> 
> v2: send to net-next.
> 
> Lijun Pan (2):
>   ibmvnic: rework to ensure SCRQ entry reads are properly ordered
>   ibmvnic: remove unnecessary rmb() inside ibmvnic_poll
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/2] ibmvnic: rework to ensure SCRQ entry reads are properly ordered
    https://git.kernel.org/netdev/net-next/c/665ab1eb18d7
  - [net-next,v2,2/2] ibmvnic: remove unnecessary rmb() inside ibmvnic_poll
    https://git.kernel.org/netdev/net-next/c/2719cb445da5

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-02-02  4:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  1:19 [PATCH net-next v2 0/2] rework the memory barrier for SCRQ entry Lijun Pan
2021-01-30  1:19 ` [PATCH net-next v2 1/2] ibmvnic: rework to ensure SCRQ entry reads are properly ordered Lijun Pan
2021-01-30  1:19 ` [PATCH net-next v2 2/2] ibmvnic: remove unnecessary rmb() inside ibmvnic_poll Lijun Pan
2021-02-02  4:30 ` 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=161224020794.9509.11960411803239623836.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=brking@linux.vnet.ibm.com \
    --cc=dnbanerg@us.ibm.com \
    --cc=drt@linux.ibm.com \
    --cc=ljp@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sukadev@linux.ibm.com \
    --cc=tlfalcon@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).