From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:45971 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726120AbgDUKxn (ORCPT ); Tue, 21 Apr 2020 06:53:43 -0400 Date: Tue, 21 Apr 2020 12:53:39 +0200 From: Christoph Hellwig Subject: Re: stop using ioctl_by_bdev in the s390 DASD driver Message-ID: <20200421105339.GA23380@lst.de> References: <20200421061226.33731-1-hch@lst.de> <20200421123256.2f5d9dbd.cohuck@redhat.com> <427b0095-6a38-5632-8e46-422c7a4a552a@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427b0095-6a38-5632-8e46-422c7a4a552a@de.ibm.com> Sender: linux-s390-owner@vger.kernel.org List-ID: To: Christian Borntraeger Cc: Cornelia Huck , Christoph Hellwig , Stefan Haberland , Jan Hoeppner , Jens Axboe , Heiko Carstens , Vasily Gorbik , linux-s390@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org On Tue, Apr 21, 2020 at 12:43:03PM +0200, Christian Borntraeger wrote: > So 3 MB seems quite a lot for special purpose Linuxes like the zfcp dumper. Does the zfcp dumper need DASD support at all? We don't have to always build in the DASD core to avoid the strange dasd-specific block_device operation, but only ensure it is built-in if it is selected at all.