All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Niklas Cassel via buildroot <buildroot@buildroot.org>,
	Niklas Cassel <cassel@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	Kilian Zinnecker <kilian.zinnecker@mail.de>
Subject: Re: [Buildroot] [PATCH v3 1/4] configs/rock5b: update to linux 6.11.3
Date: Tue, 22 Oct 2024 21:08:14 +0000	[thread overview]
Message-ID: <ZxgUPHsMJYIf8S-p@ryzen> (raw)
In-Reply-To: <20241022224631.3adcf661@windsurf>

On Tue, Oct 22, 2024 at 10:46:31PM +0200, Thomas Petazzoni wrote:
> On Wed, 16 Oct 2024 15:24:40 +0200
> Niklas Cassel via buildroot <buildroot@buildroot.org> wrote:
> 
> > From: Niklas Cassel <cassel@kernel.org>
> > 
> > A bunch of new hardware has been enabled for rock5b in linux 6.11,
> > most notably USB3 host controller support, GPU support, cpufreq
> > support, and PCIe endpoint mode support.
> > 
> > Add the dependency on host python3 that is new since linux 6.10.
> > 
> > Also add the missing dependency on openssl (which has been needed for
> > a long time, since we are using arm64 defconfig, but only shows up as
> > an error if the host system doesn't have extract-cert installed.)
> > 
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> > ---
> >  board/radxa/rock5b/patches/linux/linux.hash | 4 ++--
> >  configs/rock5b_defconfig                    | 6 ++++--
> >  2 files changed, 6 insertions(+), 4 deletions(-)
> 
> Applied to master, thanks.

Hello Thomas,

It appears that you missed the cover letter for this series, which stated:
"""
This series depends on:
https://lore.kernel.org/buildroot/20241013103341.78501-1-bernd@kuhls.net/
which adds support for linux 6.11.x.
"""

I do not see this dependency on master yet.

So I think you need to also apply the series that adds support for linux 6.11.

I don't see a reason why it hasn't been merged yet.
Bernd's first patch series that added support for 6.11 was sent in September
(2024-09-17), the series that I link to above is his V2 (even though he didn't
mark it as V2) which he sent in October (2024-10-13).


Kind regards,
Niklas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-10-22 21:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16 13:24 [Buildroot] [PATCH v3 0/4] rock5b improvements Niklas Cassel via buildroot
2024-10-16 13:24 ` [Buildroot] [PATCH v3 1/4] configs/rock5b: update to linux 6.11.3 Niklas Cassel via buildroot
2024-10-22 20:46   ` Thomas Petazzoni via buildroot
2024-10-22 21:08     ` Niklas Cassel via buildroot [this message]
2024-10-22 21:10       ` Niklas Cassel via buildroot
2024-10-22 21:14       ` Thomas Petazzoni via buildroot
2024-10-23 18:31   ` Kilian Zinnecker via buildroot
2024-10-16 13:24 ` [Buildroot] [PATCH v3 2/4] configs/rock5b: update to uboot 2024.10 Niklas Cassel via buildroot
2024-10-22 20:46   ` Thomas Petazzoni via buildroot
2024-10-16 13:24 ` [Buildroot] [PATCH v3 3/4] configs/rock5b: use the arm64 rootfs partition-type-uuid Niklas Cassel via buildroot
2024-10-22 20:49   ` Thomas Petazzoni via buildroot
2024-10-22 21:50     ` Niklas Cassel via buildroot
2024-10-23 16:19       ` Thomas Petazzoni via buildroot
2024-10-23 20:07         ` Niklas Cassel via buildroot
2024-10-16 13:24 ` [Buildroot] [PATCH v3 4/4] configs/rock5b: enable uboot-env on the SD card Niklas Cassel via buildroot
2024-10-22 20:50   ` Thomas Petazzoni via buildroot
2024-10-23 18:35     ` Niklas Cassel via buildroot
2024-10-23 19:13       ` Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZxgUPHsMJYIf8S-p@ryzen \
    --to=buildroot@buildroot.org \
    --cc=Niklas.Cassel@wdc.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=kilian.zinnecker@mail.de \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.