IronPort-SDR: lhU90do8CTsmeAm8T9YIfzYnLK5UmVYj1E9B6OHaPiWgp7iTePaGexS8gVONZotFDqllIndynb
 hJbhH5I6ezXSR0398xplgJRfsV+0t9jCOMDWgbvxTOsK8WCJLYERyQ2krlvVfcGaNBykHurAhE
 Sx/EZz+DmnqlQ8IakGBkfgr5Ow8/Tq3uph7oY8O/VCQfde0N0An33bw67L3a+GkIJkNQgEmxXQ
 pNJX0RJYzwqN37eRcKT1OmRrCx0ItwC2tCUid8a6qV9GwWJee/jD00bOetkCeTQprVfEv8MTCc
 P1U=
IronPort-SDR: dwrhhEDDXHvQr54Wm750B7xKWSS1Q9vMoqGEndODV3pfvKExRhFpbMDbdvL+InVHI8elYdMt9r
 xzJ44EpkKNIPeOD4pxhQ9ALkWzAZ88Id6CY0UcyorbC1HoKzdqs6GbdbI0NANiED6+brenG7fq
 Fth5fxlW2m8x+M5WQ8iVN/knAazid7e7q4tuPImu+wb+klrCG2IXlCGkuRAKW0QQOctmQOKFxy
 2QzSzDIGo6qMn12QSApYErjQ4QX2unItV8iNoiwWuqkm1/d6NfpA+k1TPq1kJbJm6BpF+VT6kH
 Bxo=
WDCIronportException: Internal
Message-ID: <569cb9ba-52d6-da73-dba0-cc62c91f6db2@opensource.wdc.com>
Date:   Mon, 30 Jan 2023 16:10:48 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.6.0
Subject: Re: [PATCH v3] pata_parport: add driver (PARIDE replacement)
Content-Language: en-US
To:     Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc:     Ondrej Zary <linux@zary.sk>, Sergey Shtylyov <s.shtylyov@omp.ru>,
        Tim Waugh <tim@cyberelk.net>, linux-block@vger.kernel.org,
        linux-parport@lists.infradead.org, linux-ide@vger.kernel.org,
        linux-kernel@vger.kernel.org
References: <425b5646-23e2-e271-5ca6-0f3783d39a3b@opensource.wdc.com>
 <20230123190954.5085-1-linux@zary.sk>
 <d4f7ebd5-d90d-fb96-0fad-bd129ac162dc@opensource.wdc.com>
 <e843fde8-7295-dd30-6d98-a62f63d7753c@kernel.dk>
 <20230130064815.GA31925@lst.de>
From:   Damien Le Moal <damien.lemoal@opensource.wdc.com>
Organization: Western Digital Research
In-Reply-To: <20230130064815.GA31925@lst.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/30/23 15:48, Christoph Hellwig wrote:
> On Sun, Jan 29, 2023 at 08:44:06PM -0700, Jens Axboe wrote:
>> I would prefer if we just delete it after merging this one, in the same
>> release. I don't think there's any point in delaying, as we're not
>> removing any functionality.
>>
>> You could just queue that up too when adding this patch.
> 
> I'd prefer to just deprecate.  But most importantly I want this patch
> in ASAP in some form.

I will queue it. But I think it needs a follow up to result in something
consistent with KConfig. So either deprecate or delete PARPORT. I can queue the
deprecate patch and delete in 6.4, even though I share Jen's opinion to simply
delete directly. I am still fine either way.

Jens,

If you are OK with that, can I get your ack for the deprecate patch ? Unless you
prefer taking it through the block tree. Either way is fine with me.

-- 
Damien Le Moal
Western Digital Research