[v2,0/5] defconfig: fix changed configs and refresh

Message

Max Krummenacher April 8, 2020, 2:30 p.m. UTC

Three configs have been renamed and/or changed behaviour.
Clean that by using the new config name.
With the name change to DRM_SIMPLE_BRIDGE the related
DRM_DISPLAY_CONNECTOR got introduced, enable that additionally.

Then refresh the defconfig with make defconfig savedefconfig.

The refreshed defconfig does result in a not changed .config.

Applies on linux-next/master tag: next-20200407


Changes in v2:
- additional patch adding DRM_DISPLAY_CONNECTOR as recommended by Geert and Laurent
- add reviewed-by tags

Max Krummenacher (5):
  arm64: defconfig: DRM_DUMB_VGA_DAC: follow changed config symbol name
  arm64: defconfig: add DRM_DISPLAY_CONNECTOR
  arm64: defconfig: PCIE_TEGRA194: follow changed config symbol name
  arm64: defconfig: ARCH_R8A7795: follow changed config symbol name
  arm64: defconfig: refresh

 arch/arm64/configs/defconfig | 23 +++++++++++------------
 1 file changed, 11 insertions(+), 12 deletions(-)

Comments

Arnd Bergmann April 27, 2020, 11:25 a.m. UTC | #1

On Wed, Apr 8, 2020 at 4:31 PM Max Krummenacher <[e-mail]> wrote:
>
> Three configs have been renamed and/or changed behaviour.
> Clean that by using the new config name.
> With the name change to DRM_SIMPLE_BRIDGE the related
> DRM_DISPLAY_CONNECTOR got introduced, enable that additionally.
>
> Then refresh the defconfig with make defconfig savedefconfig.
>
> The refreshed defconfig does result in a not changed .config.
>
> Applies on linux-next/master tag: next-20200407
>
>
> Changes in v2:
> - additional patch adding DRM_DISPLAY_CONNECTOR as recommended by Geert and Laurent
> - add reviewed-by tags

Thank you for the series!

When you are reasonably confident that you have done these patches correctly,
feel free to send them to [e-mail] so they make it into the
lore.kernel.org
patchwork instance and we pick them up from there.

From the description, I guess the first four are supposed to be
applied as bugfixes
for v5.7, and the last one is meant as a cleanup and queued for v5.8? Please
indicated in the cover letter what you think should happen with them, then we
can either follow that suggestion or see if anyone disagrees.

For the last patch, I want a better description, as you do not say how you made
sure that nothing else changed that needs to be addressed with a separate
patch. From the diffstat "1 file changed, 7 insertions(+), 10 deletions(-)", it
sounds like seven options got moved around but did not change behavior,
but three others have either disappeared or also got renamed. I could look
more closely to see what happened exactly, but I'd prefer this to be obvious
from the changelog.

        Arnd