lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 26 Jan 2022 08:31:22 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Arnd Bergmann <arnd@...db.de>, Shawn Guo <shawnguo@...nel.org>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 127/239] ARM: imx: rename DEBUG_IMX21_IMX27_UART to
 DEBUG_IMX27_UART

On Tue, Jan 25, 2022 at 08:15:46PM +0100, Pavel Machek wrote:
> Hi!
> 
> > [ Upstream commit b0100bce4ff82ec1ccd3c1f3d339fd2df6a81784 ]
> > 
> > Since commit 4b563a066611 ("ARM: imx: Remove imx21 support"), the config
> > DEBUG_IMX21_IMX27_UART is really only debug support for IMX27.
> > 
> > So, rename this option to DEBUG_IMX27_UART and adjust dependencies in
> > Kconfig and rename the definitions to IMX27 as further clean-up.
> > 
> > This issue was discovered with ./scripts/checkkconfigsymbols.py, which
> > reported that DEBUG_IMX21_IMX27_UART depends on the non-existing config
> > SOC_IMX21.
> 
> This is unsuitable for 4.19, as CONFIG_SOC_IMX21 is still present
> there. It is probably okay for 5.10. I did not check others.

Good point, I will drop this from 5.4 and older now.

thanks,

greg k-h

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ