Re: [Buildroot] [PATCH v2 2/2] configs/avenger96: bump Linux version to 6.6.21LTS

[Peter Korsgaard <peter@korsgaard.com>]

>>>>> "Javad" == Javad Rahimipetroudi <javad.rahimipetroudi@essensium.com> writes:

 > This patch upgrades Kernel version to 6.6.21 LTS on avenger96 board.
 > Beside that, the device tree path also modified to point the device
 > tree in proper location.

Please document when this move was done as I requested - E.G. this
commit from 6.5-rc1:

commit 724ba6751532055db75992fc6ae21c3e322e94a7
Author: Rob Herring <robh@kernel.org>
Date:   Thu May 4 18:38:52 2023 -0500

    ARM: dts: Move .dts files to vendor sub-directories

    The arm dts directory has grown to 1559 boards which makes it a bit
    unwieldy to maintain and use. Past attempts stalled out due to plans to
    move .dts files out of the kernel tree. Doing that is no longer planned
    (any time soon at least), so let's go ahead and group .dts files by
    vendors. This move aligns arm with arm64 .dts file structure.

    There's no change to dtbs_install as the flat structure is maintained on
    install.

    The naming of vendor directories is roughly in this order of preference:
    - Matching original and current SoC vendor prefix/name (e.g. ti, qcom)
    - Current vendor prefix/name if still actively sold (SoCs which have
      been aquired) (e.g. nxp/imx)
    - Existing platform name for older platforms not sold/maintained by any
      company (e.g. gemini, nspire)

    The whole move was scripted with the exception of MAINTAINERS and a few
    makefile fixups.


 > As another change, with the default root append (mmcblk1p4) in
 > 'extlinux.conf' file in the overlay directory of the board,
 > the rootfs was not possible to be detected. This file also
 > modified to point to the proper mmc block.

Also document where this comes from. I would guess it is from this
change in 5.10-rc1:

commit 21b2cec61c04bd175f0860d9411a472d5a0e7ba1
Author: Douglas Anderson <dianders@chromium.org>
Date:   Thu Sep 3 16:24:36 2020 -0700

    mmc: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in v4.4

    This is like commit 3d3451124f3d ("mmc: sdhci-msm: Prefer asynchronous
    probe") but applied to a whole pile of drivers.  This batch converts
    the drivers that appeared to be around in the v4.4 timeframe.

    Signed-off-by: Douglas Anderson <dianders@chromium.org>
    Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
    Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com> # SH_MMCIF
    Tested-by: Thierry Reding <treding@nvidia.com>
    Link: https://lore.kernel.org/r/20200903162412.1.Id501e96fa63224f77bb86b2135a5e8324ffb9c43@changeid
    Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>

Or the followup one from 6.5-rc1:

commit 3108eb2e8aa7e955a9dd3a4c1bf19a7898961822
Author: Ulf Hansson <ulf.hansson@linaro.org>
Date:   Mon Jun 12 16:37:30 2023 +0200

   mmc: mmci: Set PROBE_PREFER_ASYNCHRONOUS

   All mmc host drivers should have the asynchronous probe option enabled, but
   it seems like we failed to set it for mmci, so let's do that now.

   Fixes: 21b2cec61c04 ("mmc: Set PROBE_PREFER_ASYNCHRONOUS for drivers that existed in v4.4")
   Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
   Tested-by: Linus Walleij <linus.walleij@linaro.org>
   Tested-by: Yann Gautier <yann.gautier@foss.st.com>
   Cc: stable@vger.kernel.org
   Link: https://lore.kernel.org/r/20230612143730.210390-1-ulf.hansson@linaro.org

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot