From: patchwork-bot+netdevbpf@kernel.org
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
raspl@linux.ibm.com, ubraun@linux.ibm.com
Subject: Re: [PATCH net-next v2] net/smc: improve return codes for SMC-Dv2
Date: Sat, 31 Oct 2020 22:50:04 +0000 [thread overview]
Message-ID: <160418460471.3842.2355856936084967249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201031181938.69903-1-kgraul@linux.ibm.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sat, 31 Oct 2020 19:19:38 +0100 you wrote:
> To allow better problem diagnosis the return codes for SMC-Dv2 are
> improved by this patch. A few more CLC DECLINE codes are defined and
> sent to the peer when an SMC connection cannot be established.
> There are now multiple SMC variations that are offered by the client and
> the server may encounter problems to initialize all of them.
> Because only one diagnosis code can be sent to the client the decision
> was made to send the first code that was encountered. Because the server
> tries the variations in the order of importance (SMC-Dv2, SMC-D, SMC-R)
> this makes sure that the diagnosis code of the most important variation
> is sent.
>
> [...]
Here is the summary with links:
- [net-next,v2] net/smc: improve return codes for SMC-Dv2
https://git.kernel.org/netdev/net-next/c/3752404a68e8
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:[~2020-10-31 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 18:19 [PATCH net-next v2] net/smc: improve return codes for SMC-Dv2 Karsten Graul
2020-10-31 22:50 ` 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=160418460471.3842.2355856936084967249.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=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=ubraun@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