Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Gaël PORTAY" <gael.portay@gmail.com>
Cc: Athaariq Ardhiansyah <foss@athaariq.my.id>,
	Martin Bark <martin@barkynet.com>,
	Mahyar Koshkouei <mahyar.koshkouei@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/3] package/rpi-firmware: bump version to 1.20240529
Date: Mon, 15 Jul 2024 14:15:05 +0200	[thread overview]
Message-ID: <20240715141505.12489c82@windsurf> (raw)
In-Reply-To: <D2PZUUV1LBT7.1EDN48KIUUPUB@gmail.com>

Hello,

On Mon, 15 Jul 2024 11:10:22 +0200
Gaël PORTAY <gael.portay@gmail.com> wrote:

> In all, a bump of the rpi-firmware **SHOULD** correspond to a bump of
> the linux kernel, for every raspberrypi defconfig files (in a separate
> commit). See commit[2][3].
> 
> You will find the commit id in extra/git_hash[4] in the rpi-firmware
> tree: c1432b4bae5b6582f4d32ba381459f33c34d1424. And, you will figure out
> it corresponds to tag stable_20240529[5] in the linux-raspberrypi tree.

These rules should be written, in the rpi-firmware.mk, and probably in
the various RPi defconfigs.

> Could you update BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION accordingly in
> a dedicated commit? (I think you could use the tag name, no tested).

Yes, it can use tags.

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-15 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 16:04 [Buildroot] [PATCH v4 1/3] package/rpi-firmware: bump version to 1.20240529 Athaariq Ardhiansyah
2024-07-14 16:04 ` [Buildroot] [PATCH v4 2/3] package/raspberrypi-usbboot: bump version to master (commit 4a3d311) Athaariq Ardhiansyah
2024-07-14 16:57   ` Thomas Petazzoni via buildroot
2024-07-14 16:04 ` [Buildroot] [PATCH v4 3/3] board/raspberrypi: add support for Raspberry Pi 5 Athaariq Ardhiansyah
2024-07-14 16:59   ` Thomas Petazzoni via buildroot
2024-07-14 16:56 ` [Buildroot] [PATCH v4 1/3] package/rpi-firmware: bump version to 1.20240529 Thomas Petazzoni via buildroot
2024-07-15  9:10 ` Gaël PORTAY
2024-07-15 12:15   ` Thomas Petazzoni via buildroot [this message]
2024-07-15 16:11   ` Athaariq Ardhiansyah

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=20240715141505.12489c82@windsurf \
    --to=buildroot@buildroot.org \
    --cc=foss@athaariq.my.id \
    --cc=gael.portay@gmail.com \
    --cc=mahyar.koshkouei@gmail.com \
    --cc=martin@barkynet.com \
    --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