public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stefan Haberland <sth@linux.ibm.com>, hch@lst.de
Cc: hoeppner@linux.ibm.com, linux-s390@vger.kernel.org,
	heiko.carstens@de.ibm.com, gor@linux.ibm.com,
	linux-kernel@vger.kernel.org, borntraeger@de.ibm.com
Subject: Re: [PATCH v4 0/2] s390/dasd: remove ioctl_by_bdev from DASD driver
Date: Thu, 21 May 2020 08:22:48 -0600	[thread overview]
Message-ID: <3889844e-20eb-6b33-6bbd-109d11b0a71e@kernel.dk> (raw)
In-Reply-To: <20200519142259.102279-1-sth@linux.ibm.com>

On 5/19/20 8:22 AM, Stefan Haberland wrote:
> Hi Christoph,
> 
> here are the patches again. Reviewed and tested internally with DASD as
> well as DASD labeled virtblk devices.
> So if you agree with the two patches I have no objection against an
> inclusion.

Applied for 5.8, with Christoph's removal patch as well.

-- 
Jens Axboe

      parent reply	other threads:[~2020-05-21 14:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-19 14:22 [PATCH v4 0/2] s390/dasd: remove ioctl_by_bdev from DASD driver Stefan Haberland
2020-05-19 14:22 ` [PATCH v4 1/2] dasd: refactor dasd_ioctl_information Stefan Haberland
2020-05-19 14:22 ` [PATCH v4 2/2] s390/dasd: remove ioctl_by_bdev calls Stefan Haberland
2020-05-19 14:29   ` Christoph Hellwig
2020-10-07  9:34   ` Christian Borntraeger
2020-10-07 10:39     ` Christoph Hellwig
2020-10-07 10:44       ` Christian Borntraeger
2020-10-07 11:09         ` Stefan Haberland
2020-10-07 12:00         ` Christoph Hellwig
2020-10-07 12:09           ` Christian Borntraeger
2020-10-07 12:14             ` Christoph Hellwig
2020-10-07 12:23               ` Christian Borntraeger
2020-05-19 14:33 ` [PATCH 3/2] block: remove ioctl_by_bdev Christoph Hellwig
2020-05-19 19:03   ` Al Viro
2020-05-19 19:29     ` Christoph Hellwig
2020-05-21 14:22 ` Jens Axboe [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=3889844e-20eb-6b33-6bbd-109d11b0a71e@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=borntraeger@de.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hch@lst.de \
    --cc=heiko.carstens@de.ibm.com \
    --cc=hoeppner@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sth@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