Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp3406502pxp; Tue, 8 Mar 2022 13:46:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJyBonXZLt9Z8Saz7oOREDCiOgyymst006OhnDLoWOl8l6OyHGj9sI8tVW6v3LJBfW0UhpPl X-Received: by 2002:a17:907:1611:b0:6da:81d0:89d3 with SMTP id hb17-20020a170907161100b006da81d089d3mr15127899ejc.306.1646776003562; Tue, 08 Mar 2022 13:46:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646776003; cv=none; d=google.com; s=arc-20160816; b=A7TAYMZRptlHByPyHYDBT3NCLTTlyB25TfrUObc4R8S+Zb9klEQJ9Ax4q1cDLm7iIp WPTps9NqJWj/5reHHk7nd0+8RY7rKZcY8uCmbUbh3Qi5bWkQkehyIPp9oDFmjWIMavMy O6sGw2tSr7IuNV7w28aK1l5NU0I2kRIDrYu7Q80wl1HASrSTh+C2c+Ei/vNB4TNT+fgk F/kUcIc9o0eWHQwov1aQLdjHR5pY5ZObj5MT5uA8RTPOXwtlYrYqqkgSBlTdyKnEkjqs MGk5Xd9BE1iEi2V0SVxsTqSKAzlI3XIPNtBBSQjt4yS1WN7ocHyDrDyoQY4NJ5ZHdwYC 1cIw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=yQK4b08nGYfvhZ40IyUb0gln5g7zylhswqWDBQsvqBQ=; b=BUHfzvy13GTV9l1Lo3I8l5aOoLk5t57uh81uznojDSKh54VRe55vQVh1Ntxv7zqAtb N02E3+0m3g+i2zfIgUrpHe12QJpS1EblW+oOSx5RILn0lZVQsNHVgy75JBpeuwMbucAH t+nvHL48xTABfy91ltq2L+f2IrSNtVVOWTk7dC8i295ULspCthykEbC3mUKwU/FAjq5b ABxvlEgKgPy+D2x1r7LjMZAYA36LTqdjuyczJ+TQj+qmaf0CW2RwoC/shO+AvUbEHW/6 T5VcQSCXffsB1CnyNrXNxpDFScPLMoBM4wYsW3OJ/VpivovW2o369tKULLNGVkTFJDbr gLCQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l7-20020a056402254700b00415322bd915si18769edb.610.2022.03.08.13.46.20; Tue, 08 Mar 2022 13:46:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S245533AbiCHGzo (ORCPT + 99 others); Tue, 8 Mar 2022 01:55:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48206 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243289AbiCHGzn (ORCPT ); Tue, 8 Mar 2022 01:55:43 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D89C22B251; Mon, 7 Mar 2022 22:54:47 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 4147068AFE; Tue, 8 Mar 2022 07:54:44 +0100 (CET) Date: Tue, 8 Mar 2022 07:54:43 +0100 From: Christoph Hellwig To: Ondrej Zary Cc: Christoph Hellwig , Damien Le Moal , Jens Axboe , Tim Waugh , linux-block@vger.kernel.org, linux-parport@lists.infradead.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] pata_parport: paride replacement Message-ID: <20220308065443.GA24269@lst.de> References: <20220305201411.501-1-linux@zary.sk> <20220306085825.GA22425@lst.de> <202203061136.36700.linux@zary.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202203061136.36700.linux@zary.sk> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Mar 06, 2022 at 11:36:36AM +0100, Ondrej Zary wrote: > On Sunday 06 March 2022 09:58:25 Christoph Hellwig wrote: > > Hi Ondrej, > > > > I just took a quick glance and it seems like the actual protocol > > modules still are basically almost exactly the same ones as the > > paride ones. Is there a way to just keep the existing modules? > > > > The only big thing I noticed is the host template, but at least > > for the transitional periode we could probably allocate that > > dynamically in the core. I think would reduce the amount of code > > churn nicely and make review much easier. > > Yes, only small changes in the protocol modules regarding (un)registration. > > Getting the original modules work with pata_parport (like in 1st preview) required some hacks that break paride (disabling EXPORT_SYMBOLs in paride). > > Maybe the protocol modules can be moved (git mv) from paride and then patched? A copy would be better but there's no "git cp". Hmm, how would be break the old PARIDE code? You'd need the new libata support exlusive to the old PARIDE code so that only one of them can export the registration symbols at a time. The git-mv can happen once the old paride code is removed after a release or two. > > -- > Ondrej Zary ---end quoted text---