[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73a04afaf658292c05ef27117c60b21d@milecki.pl>
Date: Mon, 06 Mar 2023 14:57:03 +0100
From: Rafał Miłecki <rafal@...ecki.pl>
To: Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Michael Walle <michael@...le.cc>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devicetree@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Robert Marko <robert.marko@...tura.hr>,
Luka Perkov <luka.perkov@...tura.hr>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH 0/8] nvmem: Let layout drivers be modules
On 2023-03-06 14:35, Miquel Raynal wrote:
> Hi Michael,
>
> michael@...le.cc wrote on Mon, 06 Mar 2023 14:01:34 +0100:
>
>> > Miquel Raynal (8):
>> > of: Fix modalias string generation
>> > of: Change of_device_get_modalias() main argument
>> > of: Create an of_device_request_module() receiving an OF node
>> > nvmem: core: Fix error path ordering
>> > nvmem: core: Handle the absence of expected layouts
>> > nvmem: core: Request layout modules loading
>> > nvmem: layouts: sl28vpd: Convert layout driver into a module
>> > nvmem: layouts: onie-tlv: Convert layout driver into a module
>>
>> With the fixes series [1] applied:
>
> Thanks for the series! Looks good to me. I believe both series can live
> in separate tress, any reason why we would like to avoid this? I am
> keen
> to apply [1] into the mtd tree rather soon.
Given past events with nvmem patches I'm against that.
Let's wait for Srinivas to collect pending patches, let them spend a
moment in linux-next maybe, ask Srinivas to send them to Greg early if
he can. That way maybe you can merge Greg's branch (assuming he doesn't
rebase).
Powered by blists - more mailing lists