netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	linux-s390@vger.kernel.org, hca@linux.ibm.com,
	agordeev@linux.ibm.com
Subject: Re: [PATCH net-next 0/2] s390/net: updates 2022-02-21
Date: Wed, 23 Feb 2022 00:30:10 +0000	[thread overview]
Message-ID: <164557621078.11578.8543243178652229719.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220221145633.3869621-1-wintera@linux.ibm.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 21 Feb 2022 15:56:31 +0100 you wrote:
> Hello Dave & Jakub,
> 
> please apply the following patches to netdev's net-next tree.
> 
> Just cleanup. No functional changes, as currently virt=phys in s390.
> 
> Thank you
> Alexandra
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] s390/iucv: sort out physical vs virtual pointers usage
    https://git.kernel.org/netdev/net-next/c/ab847d03a5e4
  - [net-next,2/2] s390/net: sort out physical vs virtual pointers usage
    https://git.kernel.org/netdev/net-next/c/1bb7e8dff896

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



      parent reply	other threads:[~2022-02-23  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 14:56 [PATCH net-next 0/2] s390/net: updates 2022-02-21 Alexandra Winter
2022-02-21 14:56 ` [PATCH net-next 1/2] s390/iucv: sort out physical vs virtual pointers usage Alexandra Winter
2022-02-21 14:56 ` [PATCH net-next 2/2] s390/net: " Alexandra Winter
2022-02-23  0: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=164557621078.11578.8543243178652229719.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=davem@davemloft.net \
    --cc=hca@linux.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=wintera@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).