From: Eugene Syromiatnikov <esyr@redhat.com>
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, Ursula Braun <ubraun@linux.ibm.com>,
Karsten Graul <kgraul@linux.ibm.com>
Subject: [PATCH net v2 0/3] net/smc: move some definitions to UAPI
Date: Fri, 20 Sep 2019 17:41:47 +0200 [thread overview]
Message-ID: <cover.1568993930.git.esyr@redhat.com> (raw)
Hello.
As of now, it's a bit difficult to use SMC protocol, as significant part
of definitions related to it are defined in private headers and are not
part of UAPI. The following commits move some definitions to UAPI,
making them readily available to the user space.
Changes since v1[1]:
* Patch "provide fallback diagnostic codes in UAPI" is updated
in accordance with the updated set of diagnostic codes.
[1] https://lkml.org/lkml/2018/10/7/177
Eugene Syromiatnikov (3):
uapi, net/smc: move protocol constant definitions to UAPI
uapi, net/smc: provide fallback diagnostic codes in UAPI
uapi, net/smc: provide socket state constants in UAPI
include/uapi/linux/smc.h | 32 +++++++++++++++++++++++++++++++-
include/uapi/linux/smc_diag.h | 17 +++++++++++++++++
net/smc/smc.h | 22 ++--------------------
net/smc/smc_clc.h | 22 ----------------------
4 files changed, 50 insertions(+), 43 deletions(-)
--
2.1.4
next reply other threads:[~2019-09-20 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 15:41 Eugene Syromiatnikov [this message]
2019-09-20 15:41 ` [PATCH net v2 1/3] uapi, net/smc: move protocol constant definitions to UAPI Eugene Syromiatnikov
2019-09-20 15:41 ` [PATCH net v2 2/3] uapi, net/smc: provide fallback diagnostic codes in UAPI Eugene Syromiatnikov
2019-09-20 15:42 ` [PATCH net v2 3/3] uapi, net/smc: provide socket state constants " Eugene Syromiatnikov
2019-09-23 15:27 ` [PATCH net v2 0/3] net/smc: move some definitions to UAPI Ursula Braun
2019-09-24 14:52 ` David Miller
2019-09-25 12:10 ` Ursula Braun
2019-09-25 14:16 ` David Miller
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=cover.1568993930.git.esyr@redhat.com \
--to=esyr@redhat.com \
--cc=davem@davemloft.net \
--cc=kgraul@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).