From: Ursula Braun <ubraun@linux.ibm.com>
To: Eugene Syromiatnikov <esyr@redhat.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Karsten Graul <kgraul@linux.ibm.com>,
Hans Wippel <hwippel@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [RFC PATCH net 0/3] net/smc: move some definitions to UAPI
Date: Tue, 9 Oct 2018 17:43:03 +0200 [thread overview]
Message-ID: <3ba9cb5c-8ad9-70ab-3d32-2226a6e9f39a@linux.ibm.com> (raw)
In-Reply-To: <cover.1538929504.git.esyr@redhat.com>
On 10/07/2018 06:34 PM, Eugene Syromiatnikov wrote:
> 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 user space.
>
>
> Eugene Syromiatnikov (3):
> uapi, net/smc: move protocol constant definitions to UAPI
> uapi, net/smc: provide fallback diagnosis codes in UAPI
> uapi, net/smc: provide socket state constants in UAPI
>
> include/uapi/linux/smc.h | 26 +++++++++++++++++++++++++-
> include/uapi/linux/smc_diag.h | 17 +++++++++++++++++
> net/smc/smc.h | 22 ++--------------------
> net/smc/smc_clc.h | 16 ----------------
> 4 files changed, 44 insertions(+), 37 deletions(-)
>
Hello Eugene,
I am OK with your 3 patches.
Thanks, Ursula
prev parent reply other threads:[~2018-10-09 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-07 16:34 Eugene Syromiatnikov
2018-10-07 16:35 ` [RFC PATCH net 1/3] uapi, net/smc: move protocol constant " Eugene Syromiatnikov
2018-10-07 16:35 ` [RFC PATCH net 2/3] uapi, net/smc: provide fallback diagnosis codes in UAPI Eugene Syromiatnikov
2018-10-07 16:35 ` [RFC PATCH net 3/3] uapi, net/smc: provide socket state constants " Eugene Syromiatnikov
2018-10-09 15:43 ` Ursula Braun [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=3ba9cb5c-8ad9-70ab-3d32-2226a6e9f39a@linux.ibm.com \
--to=ubraun@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=esyr@redhat.com \
--cc=hwippel@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®