From: Stefan Haberland <sth@linux.ibm.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org,
Jan Hoeppner <hoeppner@linux.ibm.com>,
linux-s390@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH v2 00/10] DASD FC endpoint security
Date: Mon, 12 Oct 2020 21:06:37 +0200 [thread overview]
Message-ID: <20201012183550.GA12341@imap.linux.ibm.com> (raw)
In-Reply-To: <20201008131336.61100-1-sth@linux.ibm.com>
Hi Jens,
quick ping. Are you going to apply this for 5.10?
Best regards,
Stefan
Stefan Haberland <sth@linux.ibm.com> schrieb am Thu, 08. Oct 15:13:
> Hi Jens,
>
> please apply the following patches that add a new DASD feature to show
> fibre channel endpoint security.
>
> The patches apply on you for-next branch and are intended for 5.10.
>
> The s390/cio patches should also go upstream through your tree this time
> since they are required for the DASD patches to build.
>
> Best regards,
> Stefan
>
> v1->v2:
> - fix memleak in "s390/dasd: Fix operational path inconsistency"
> - add comment suggested by Cornelia Huck
>
> Jan Höppner (7):
> s390/dasd: Remove unused parameter from dasd_generic_probe()
> s390/dasd: Move duplicate code to separate function
> s390/dasd: Store path configuration data during path handling
> s390/dasd: Fix operational path inconsistency
> s390/dasd: Display FC Endpoint Security information via sysfs
> s390/dasd: Prepare for additional path event handling
> s390/dasd: Process FCES path event notification
>
> Sebastian Ott (1):
> s390/cio: Export information about Endpoint-Security Capability
>
> Vineeth Vijayan (2):
> s390/cio: Provide Endpoint-Security Mode per CU
> s390/cio: Add support for FCES status notification
>
> arch/s390/include/asm/ccwdev.h | 2 +
> arch/s390/include/asm/cio.h | 1 +
> drivers/s390/block/dasd.c | 22 ++--
> drivers/s390/block/dasd_devmap.c | 109 +++++++++++++++++++
> drivers/s390/block/dasd_eckd.c | 175 +++++++++++++++++++++----------
> drivers/s390/block/dasd_fba.c | 2 +-
> drivers/s390/block/dasd_int.h | 111 +++++++++++++++++++-
> drivers/s390/cio/chp.c | 15 +++
> drivers/s390/cio/chp.h | 1 +
> drivers/s390/cio/chsc.c | 145 +++++++++++++++++++++++--
> drivers/s390/cio/chsc.h | 3 +-
> drivers/s390/cio/device.c | 15 ++-
> 12 files changed, 523 insertions(+), 78 deletions(-)
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-10-12 19:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 13:13 [PATCH v2 00/10] DASD FC endpoint security Stefan Haberland
2020-10-08 13:13 ` [PATCH v2 01/10] s390/cio: Export information about Endpoint-Security Capability Stefan Haberland
2020-10-08 13:13 ` [PATCH v2 02/10] s390/cio: Provide Endpoint-Security Mode per CU Stefan Haberland
2020-10-08 13:13 ` [PATCH v2 03/10] s390/cio: Add support for FCES status notification Stefan Haberland
2020-10-08 13:13 ` [PATCH v2 04/10] s390/dasd: Remove unused parameter from dasd_generic_probe() Stefan Haberland
2020-10-08 14:13 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 05/10] s390/dasd: Move duplicate code to separate function Stefan Haberland
2020-10-08 14:16 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 06/10] s390/dasd: Store path configuration data during path handling Stefan Haberland
2020-10-08 14:21 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 07/10] s390/dasd: Fix operational path inconsistency Stefan Haberland
2020-10-08 14:37 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 08/10] s390/dasd: Display FC Endpoint Security information via sysfs Stefan Haberland
2020-10-08 14:43 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 09/10] s390/dasd: Prepare for additional path event handling Stefan Haberland
2020-10-08 14:48 ` Cornelia Huck
2020-10-08 13:13 ` [PATCH v2 10/10] s390/dasd: Process FCES path event notification Stefan Haberland
2020-10-08 14:54 ` Cornelia Huck
2020-10-08 14:56 ` Jan Höppner
2020-10-12 19:06 ` Stefan Haberland [this message]
2020-10-12 19:33 ` [PATCH v2 00/10] DASD FC endpoint security Jens Axboe
2020-10-12 19:50 ` Stefan Haberland
2020-10-13 19:40 ` Jens Axboe
2020-10-13 20:15 ` Stefan Haberland
2020-10-14 1:19 ` Jens Axboe
2020-11-10 15:50 ` Stefan Haberland
2020-11-11 16:20 ` Jens Axboe
2020-11-12 13:27 ` Stefan Haberland
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=20201012183550.GA12341@imap.linux.ibm.com \
--to=sth@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hoeppner@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-s390@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.