[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a1knYa-UHBz4Z0XNPDiM7Qd7GvVV-wHXfjMWbA9MxCcXw@mail.gmail.com>
Date: Wed, 3 Mar 2021 18:57:50 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Alistair Francis <alistair@...stair23.me>
Cc: Olof Johansson <olof@...om.net>, Rob Herring <robh+dt@...nel.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Sascha Hauer <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
DTML <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alistair Francis <alistair23@...il.com>
Subject: Re: [PATCH v3 3/3] ARM: imx_v6_v7_defconfig: Regenerate
On Thu, Feb 4, 2021 at 4:03 AM Alistair Francis <alistair@...stair23.me> wrote:
>
> Run make imx_v6_v7_defconfig; make savedefconfig to regenerate the
> defconfig.
>
> Signed-off-by: Alistair Francis <alistair@...stair23.me>
I need to do something across all our defconfigs at some point, but I want
to be done more thoroughly:
For any option or group of options that disappears from a defconfig file, I
want to see one patch (ideally across all such files) that explains why
the option that used to be intentionally enable is no longer there. If it
got renamed or replaced by something else, that should be set instead.
If there is a new dependency, we may need to enable that in addition
to the old option, rather than dropping it silently.
For options that just move around in the file, I would group them in
a final cleanup patch.
Arnd
Powered by blists - more mailing lists