From: patchwork-bot+netdevbpf@kernel.org
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
kgraul@linux.ibm.com
Subject: Re: [PATCH net-next 0/3] s390/qeth: updates 2021-07-20
Date: Tue, 20 Jul 2021 13:30:10 +0000 [thread overview]
Message-ID: <162678781047.19709.13716919959471345433.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210720063849.2646776-1-jwi@linux.ibm.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Tue, 20 Jul 2021 08:38:46 +0200 you wrote:
> Hi Dave & Jakub,
>
> please apply the following patch series for qeth to netdev's net-next tree.
>
> This removes the deprecated support for OSN-mode devices, and does some
> follow-on cleanups.
>
> [...]
Here is the summary with links:
- [net-next,1/3] s390/qeth: remove OSN support
https://git.kernel.org/netdev/net-next/c/a8c7629c622b
- [net-next,2/3] s390/qeth: clean up QETH_PROT_* naming
https://git.kernel.org/netdev/net-next/c/a37cfa28ebdc
- [net-next,3/3] s390/qeth: clean up device_type management
https://git.kernel.org/netdev/net-next/c/ae57ea7a19b7
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-07-20 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 6:38 [PATCH net-next 0/3] s390/qeth: updates 2021-07-20 Julian Wiedmann
2021-07-20 6:38 ` [PATCH net-next 1/3] s390/qeth: remove OSN support Julian Wiedmann
2021-07-20 6:38 ` [PATCH net-next 2/3] s390/qeth: clean up QETH_PROT_* naming Julian Wiedmann
2021-07-20 6:38 ` [PATCH net-next 3/3] s390/qeth: clean up device_type management Julian Wiedmann
2021-07-20 13: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=162678781047.19709.13716919959471345433.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.