Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp3376627ybb; Tue, 31 Mar 2020 04:06:33 -0700 (PDT) X-Google-Smtp-Source: ADFU+vu3c58EuVfjV0kKT4u8vFGaBUCQstl98k5S853WmsWt5P7IrWSWuqJK8YiTpTD+j2+U/hva X-Received: by 2002:a9d:2215:: with SMTP id o21mr7685772ota.113.1585652793776; Tue, 31 Mar 2020 04:06:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585652793; cv=none; d=google.com; s=arc-20160816; b=IhbIdvVaO6AymmxJesl8DjI3OeBcls+MM/xMJGt4ie4wp0N96xwpz7ixHjnqaktitU KYsSzwcshaMUYWBCG+LK0sYK/F+1/jnUFTAaJZfYbjF6tdujK5a3dquxs730j1lt1BgH N9Jq6uBhEpjfVPyAN78gEjB0lZHnDPa9wL+lExegIi5Uvd7G5oc8AJ8aKgMHRda1B+lS tVP3vXV+EvOKyc3TgQMDRkeO1lE1l0jNL4F6/44lGW1PTe6yp2T9Nig4AFUAUN0JavGo ROBGPyRclctVgwBkza96T+b8uanqmN7pnlFMvB5JzSw/sXQ2Ky3P5xFjXhwnMBF0h6A7 sDaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=bO6sv8AR4QZ/MIrVOnbLy/+eskJrMpwGhST5uCikYCU=; b=X6HkqkQDbcQW+w5ATFK0E+S/JZx+heF1KccBcmu4vNibg2vpgjtz88nraShIP7ctGq Y3bXIbyYaQ2CACH4aCT0Sgx/rFzCZ4104GxdWC8/dGypLynE1gYiyJBzFzqoTFetE8IQ AEBERDmOyb+xqEVVklgtJxMhy5fRIHdlUzO+ONaktQuXh8AboouOuJxia4K5ETWA7Mb1 Xt29uB98B+CiiFSz/5+vE+3nFIhUvO5eHpqbHqXcUV+6kF93K0LjzwacyMglruYJG0Tf cB/v9iV2NIlEXvxKAKR94cSDasvD2Q8PoNkmkMrrFoFQ6oWNbuZ+wwXX3dHXxe0dqxQW qJpA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f23si608295oti.69.2020.03.31.04.06.18; Tue, 31 Mar 2020 04:06:33 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730462AbgCaLEn (ORCPT + 99 others); Tue, 31 Mar 2020 07:04:43 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:34203 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730377AbgCaLEm (ORCPT ); Tue, 31 Mar 2020 07:04:42 -0400 Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 02VB1a4e024578; Tue, 31 Mar 2020 13:01:36 +0200 Date: Tue, 31 Mar 2020 13:01:36 +0200 From: Willy Tarreau To: Christoph Hellwig Cc: Denis Efremov , Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, "David S. Miller" , Benjamin Herrenschmidt , Geert Uytterhoeven , Helge Deller , Ian Molton , Ivan Kokshaysky , Matt Turner , Richard Henderson , Russell King , Thomas Bogendoerfer , x86@kernel.org Subject: Re: [PATCH 00/23] Floppy driver cleanups Message-ID: <20200331110136.GB24562@1wt.eu> References: <20200331094054.24441-1-w@1wt.eu> <20200331101019.GA6299@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200331101019.GA6299@infradead.org> User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Christoph, On Tue, Mar 31, 2020 at 03:10:19AM -0700, Christoph Hellwig wrote: > Hi Willy, > > given that you are actively maintaining the floppy driver now, No no no I'm not! Denis is :-) Really, I mean I just proposed some help to clean up this mess after being tricked into not believing a bug report just because the code was too confusing. > any > chance I could trick you into proper highmem handling? I've been trying > to phase out block layer bounce buffering, and any help from a competent > maintainer to move their drivers to properly support highmem by kmapping > for PIO/MMIO I/O would be very helpful. I'm not sure what this implies regarding this code, to be honest. It's very tricky and implements sort of a state machine using function pointers within its interrupt handler so you never know exactly what accesses what, and quite a part of it remains obscure to me :-/ I can accept to help, I can even run tests since I still have running hardware, but I'd at least need some guidance. And probably Denis would know better than me there. Also I doubt we'd get sufficient testing on less common archs. While I do have sparc64/parisc/alpha available, I haven't booted a recent kernel on any of them for a while (2.4 used to be the last ones), and I'm not sure it's reasonable to go into such changes without proper testing. What do you think ? Willy