[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <221b0b7c-1879-4944-b9c4-cfb9fad9ae91@ghiti.fr>
Date: Thu, 12 Jun 2025 15:12:09 +0200
From: Alexandre Ghiti <alex@...ti.fr>
To: Yixun Lan <dlan@...too.org>
Cc: Conor Dooley <conor@...nel.org>, Paul Walmsley
<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Guodong Xu <guodong@...cstar.com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org,
spacemit@...ts.linux.dev
Subject: Re: [PATCH] riscv: defconfig: run savedefconfig to reorder it
On 6/12/25 11:32, Yixun Lan wrote:
> Hi Alexandre,
>
> On 10:37 Thu 12 Jun , Alexandre Ghiti wrote:
>> Hi Yixun,
>>
>> On 6/11/25 16:56, Yixun Lan wrote:
>>> Changes to defconfig should be always updated via 'make
>>> savedefconfig', run this command to make it aligned again.
>>>
>>> This will ease the effort of reviewing changes of defconfig
>>> in the future.
>>>
>>> Signed-off-by: Yixun Lan <dlan@...too.org>
>>> ---
>>> Update PDMA config bring in unnecessary changes[1], let's fix
>>> it by run savedefconfig first.
>>
>> It would be easier if this patch was part of the PDMA series since the
>> last patch will depend on it: @Guodong can you integrate this patch to
>> your next revision of your patchset?
>>
> I'd rather make this patch independent, as nothing strongly ralated with PDMA,
> and it probably would take several rounds for PDMA patch to be settled down..
>
> Besides, there is no problem for PDMA patch to depend on this patch if
> needed (easy to use b4 to handle this..)
>
> The idea here is to get this patch merged as early as possible, as it's
> quite straightforward, and other people may have similar problem instead
> of PDMA here
Ok makes sense, so let's Guodong deal with that then.
Thanks,
Alex
>
>> Thanks,
>>
>> Alex
>>
Powered by blists - more mailing lists