From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jamie Gibbons via buildroot <buildroot@buildroot.org>
Cc: Jamie Gibbons <jamie.gibbons@microchip.com>,
Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
Subject: Re: [Buildroot] [PATCH v3 1/2] configs/beaglev_fire: update custom tarballs
Date: Thu, 15 Aug 2024 11:02:51 +0200 [thread overview]
Message-ID: <20240815110251.550760af@windsurf> (raw)
In-Reply-To: <20240809085334.3530176-2-jamie.gibbons@microchip.com>
On Fri, 9 Aug 2024 09:53:33 +0100
Jamie Gibbons via buildroot <buildroot@buildroot.org> wrote:
> The Linux kernel and U-Boot custom tarballs were updated incorrectly
> in commit 8ce97fd550d6. Update these to select specific release tags
> instead of branches. Update the U-Boot and Linux hashes to match
> these changes.
>
> Fixes: 8ce97fd550d6 ("configs/beaglev_fire: bump Linux and U-Boot")
>
> Signed-off-by: Jamie Gibbons <jamie.gibbons@microchip.com>
> Tested-by: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
> ---
> board/beagleboard/beaglev_fire/patches/linux/linux.hash | 2 +-
> board/beagleboard/beaglev_fire/patches/uboot/uboot.hash | 2 +-
> configs/beaglev_fire_defconfig | 4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
Thanks, patches applied to our master branch!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-15 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 8:53 [Buildroot] [PATCH v3 0/2] fix mpfs custom tarballs Jamie Gibbons via buildroot
2024-08-09 8:53 ` [Buildroot] [PATCH v3 1/2] configs/beaglev_fire: update " Jamie Gibbons via buildroot
2024-08-15 9:02 ` Thomas Petazzoni via buildroot [this message]
2024-08-09 8:53 ` [Buildroot] [PATCH v3 2/2] configs/microchip_mpfs_icicle: " Jamie Gibbons 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=20240815110251.550760af@windsurf \
--to=buildroot@buildroot.org \
--cc=jamie.gibbons@microchip.com \
--cc=prajna.rajendrakumar@microchip.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