Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Matyukevich <geomatsi@gmail.com>
To: Romain Naour <romain.naour@smile.fr>
Cc: buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Romain Naour <romain.naour@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Bernd Kuhls <bernd@kuhls.net>
Subject: Re: [Buildroot] [PATCH 0/3] {linux, linux-headers}: add support for 6.12
Date: Wed, 11 Dec 2024 22:41:50 +0300	[thread overview]
Message-ID: <Z1nq_gneO4ORw3EG@curiosity> (raw)
In-Reply-To: <c4759881-c7b1-47be-b640-3a45d856fc7e@smile.fr>

Hi Romain,

On Wed, Dec 11, 2024 at 08:06:42PM +0100, Romain Naour wrote:
> Hello All,
> 
> Le 11/12/2024 à 14:43, Romain Naour a écrit :
> > Hello Sergey,
> > 
> > Le 08/12/2024 à 22:46, Sergey Matyukevich a écrit :
> >> Hi Thomas, Bernd, and all
> >>
> >> I have been waiting for the new LTS Linux v6.12 in Buildroot to start
> >> sending Christmas updates for some of my OrangePi boards. Now v6.12.3
> >> is already available, but the latest kernel is still have 6.11.x.
> >> So I decided to undertake a copy-paste exercise using the latest kernel
> >> and headers update series by Bernd. Hope I didn't miss a thing taking
> >> into account that this is a new LTS.
> > 
> > Everything seems good so far :)
> 
> Except I missed the discussion about the out of tree DTBs issue reported by
> Chris Packham and Edgar Bonet [1] :-(
> 
> [1]
> https://lore.kernel.org/buildroot/dcbd3f77-e737-41a2-9f23-87141d0bdf9b@grenoble.cnrs.fr/

IIUC this out-of-tree DTB issue can be handled separately. As we
discussed previously in this email thread, updating latest Linux
version to v6.12 and further does not break those 5 boards now.

Regards,
Sergey

> >> Regards,
> >> Sergey
> >>
> >> Sergey Matyukevich (3):
> >>   {toolchain, linux-headers}: add support for 6.12 headers
> >>   linux: bump latest version to 6.12
> >>   package/linux-headers: drop 6.11.x option
> >>
> >>  Config.in.legacy                                 |  7 +++++++
> >>  linux/Config.in                                  |  6 +++---
> >>  linux/linux.hash                                 |  2 +-
> >>  package/linux-headers/Config.in.host             | 16 ++++++++++------
> >>  toolchain/Config.in                              |  5 +++++
> >>  .../toolchain-external-custom/Config.in.options  |  6 +++++-
> >>  6 files changed, 31 insertions(+), 11 deletions(-)
> >>
> > 
> 
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-12-11 19:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 21:46 [Buildroot] [PATCH 0/3] {linux, linux-headers}: add support for 6.12 Sergey Matyukevich
2024-12-08 21:46 ` [Buildroot] [PATCH 1/3] {toolchain, linux-headers}: add support for 6.12 headers Sergey Matyukevich
2024-12-08 21:46 ` [Buildroot] [PATCH 2/3] linux: bump latest version to 6.12 Sergey Matyukevich
2024-12-08 21:46 ` [Buildroot] [PATCH 3/3] package/linux-headers: drop 6.11.x option Sergey Matyukevich
2024-12-09  8:11 ` [Buildroot] [PATCH 0/3] {linux, linux-headers}: add support for 6.12 Edgar Bonet
2024-12-10 20:43   ` Sergey Matyukevich
2024-12-11 11:34     ` Edgar Bonet
2024-12-11 18:26       ` Chris Packham
2024-12-13 10:09         ` Michael Walle via buildroot
2024-12-13 13:30           ` Sergey Matyukevich
2024-12-13 15:40             ` Edgar Bonet
2024-12-13 10:11     ` Michael Walle via buildroot
2024-12-11 13:43 ` Romain Naour via buildroot
2024-12-11 19:06   ` Romain Naour via buildroot
2024-12-11 19:41     ` Sergey Matyukevich [this message]

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=Z1nq_gneO4ORw3EG@curiosity \
    --to=geomatsi@gmail.com \
    --cc=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=romain.naour@gmail.com \
    --cc=romain.naour@smile.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox