From: patchwork-bot+netdevbpf@kernel.org
To: Wenjia Zhang <wenjia@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, hca@linux.ibm.com, kgraul@linux.ibm.com,
wintera@linux.ibm.com, jaka@linux.ibm.com, raspl@linux.ibm.com,
tonylu@linux.alibaba.com
Subject: Re: [PATCH net-next 0/2] smc: Updates 2023-03-01
Date: Wed, 15 Mar 2023 08:20:20 +0000 [thread overview]
Message-ID: <167886842088.29094.16124554092676505653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313101032.13180-1-wenjia@linux.ibm.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 13 Mar 2023 11:10:30 +0100 you wrote:
> The 1st patch is to make implements later do not need to adhere to a
> specific SEID format. The 2nd patch does some cleanup.
>
> Stefan Raspl (2):
> net/smc: Introduce explicit check for v2 support
> net/ism: Remove extra include
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/smc: Introduce explicit check for v2 support
https://git.kernel.org/netdev/net-next/c/f947568e2580
- [net-next,2/2] net/ism: Remove extra include
https://git.kernel.org/netdev/net-next/c/298c91dc40e5
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:[~2023-03-15 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 10:10 [PATCH net-next 0/2] smc: Updates 2023-03-01 Wenjia Zhang
2023-03-13 10:10 ` [PATCH net-next 1/2] net/smc: Introduce explicit check for v2 support Wenjia Zhang
2023-03-13 11:19 ` Tony Lu
2023-03-13 10:10 ` [PATCH net-next 2/2] net/ism: Remove extra include Wenjia Zhang
2023-03-13 11:15 ` Tony Lu
2023-03-15 8:20 ` 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=167886842088.29094.16124554092676505653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hca@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=raspl@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--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).