From: patchwork-bot+netdevbpf@kernel.org
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, hca@linux.ibm.com,
raspl@linux.ibm.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net/smc: updates 2021-06-02
Date: Thu, 03 Jun 2021 21:00:05 +0000 [thread overview]
Message-ID: <162275400512.32659.7809586894785729146.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210602085626.2877926-1-kgraul@linux.ibm.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 2 Jun 2021 10:56:24 +0200 you wrote:
> Please apply the following patch series for smc to netdev's net-next tree.
>
> Both patches are cleanups and remove unnecessary code.
>
> Julian Wiedmann (1):
> net/smc: no need to flush smcd_dev's event_wq before destroying it
>
> [...]
Here is the summary with links:
- [net-next,1/2] net/smc: avoid possible duplicate dmb unregistration
https://git.kernel.org/netdev/net-next/c/f8e0a68babae
- [net-next,2/2] net/smc: no need to flush smcd_dev's event_wq before destroying it
https://git.kernel.org/netdev/net-next/c/5e4a43ceb22a
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-06-03 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 8:56 [PATCH net-next 0/2] net/smc: updates 2021-06-02 Karsten Graul
2021-06-02 8:56 ` [PATCH net-next 1/2] net/smc: avoid possible duplicate dmb unregistration Karsten Graul
2021-06-02 8:56 ` [PATCH net-next 2/2] net/smc: no need to flush smcd_dev's event_wq before destroying it Karsten Graul
2021-06-03 21: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=162275400512.32659.7809586894785729146.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.