[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7a2f5b2f-3ed9-eabb-6c9b-dcb2bfe82a08@kernel.dk>
Date: Mon, 30 Jan 2023 08:25:01 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
Christoph Hellwig <hch@....de>
Cc: Ondrej Zary <linux@...y.sk>, Sergey Shtylyov <s.shtylyov@....ru>,
Tim Waugh <tim@...erelk.net>, linux-block@...r.kernel.org,
linux-parport@...ts.infradead.org, linux-ide@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] pata_parport: add driver (PARIDE replacement)
On 1/30/23 12:10 AM, Damien Le Moal wrote:
> 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.
Yeah I'd be happy to ack that, did you post it? You can add my ack to the
new driver, fine with that now.
--
Jens Axboe
Powered by blists - more mailing lists