[PATCH 13/21] Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig

[Jaehoon Chung]

> -----Original Message-----
> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Simon Glass
> Sent: Tuesday, November 1, 2022 4:27 AM
> To: Tom Rini <trini at konsulko.com>
> Cc: u-boot at lists.denx.de
> Subject: Re: [PATCH 13/21] Convert CONFIG_SYS_MMC_MAX_DEVICE to Kconfig
> 
> On Sun, 30 Oct 2022 at 10:37, Tom Rini <trini at konsulko.com> wrote:
> >
> > On Sat, Oct 29, 2022 at 07:43:36PM -0600, Simon Glass wrote:
> > > Hi Tom,
> > >
> > > On Fri, 28 Oct 2022 at 18:29, Tom Rini <trini at konsulko.com> wrote:
> > > >
> > > > This converts the following to Kconfig:
> > > >    CONFIG_SYS_MMC_MAX_DEVICE
> > > >
> > > > Signed-off-by: Tom Rini <trini at konsulko.com>
> > > > ---
> > > >  api/Kconfig                        |  5 +++++
> > > >  api/api_storage.c                  |  4 ----
> > > >  include/configs/am335x_evm.h       | 18 ------------------
> > > >  include/configs/stm32mp13_common.h |  3 ---
> > > > include/configs/stm32mp15_common.h |  3 ---
> > > >  include/configs/sunxi-common.h     |  2 --
> > > >  include/configs/tegra-common.h     |  7 -------
> > > >  include/configs/zynq-common.h      |  3 ---
> > > >  8 files changed, 5 insertions(+), 40 deletions(-)
> > >
> > > It seems odd that none of the boards end up with a defconfig setting
> > > it to 2 or 3.
> >
> > What happened here is that boards were setting the value to something
> > else, but never using it.
> 
> Ah OK, that's good to fix.
> 
> Reviewed-by: Simon Glass <sjg at chromium.org>

Reviewed-by: Jaehoon Chung <jh80.chung at samsung.com>