Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Vincent Stehlé" <vincent.stehle@arm.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3 next] package/edk2-platforms: bump in sync with edk2-stable202208
Date: Sun, 4 Dec 2022 14:05:34 +0100	[thread overview]
Message-ID: <20221204140534.5f6d0539@windsurf> (raw)
In-Reply-To: <20221201183337.1588407-2-vincent.stehle@arm.com>

On Thu,  1 Dec 2022 19:33:35 +0100
Vincent Stehlé <vincent.stehle@arm.com> wrote:

> Bump the edk2-platforms commit to the one corresponding to version
> edk2-stable202208 of edk2, based on the timestamps.
> 
> Note: the Marvell Armada Devicetree files have been moved out of
> edk2-platforms by commit 4b53da6b12a8 ("Marvell/Armada7k8k: Remove device
> tree sources from edk2-platforms") and they are now in edk2-non-osi.
> 
> Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
> Cc: Dick Olsson <hi@senzilla.io>
> ---

Applied to next, thanks.

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

  reply	other threads:[~2022-12-04 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 18:33 [Buildroot] [PATCH 0/3 next] bump edk2 version Vincent Stehlé
2022-12-01 18:33 ` [Buildroot] [PATCH 1/3 next] package/edk2-platforms: bump in sync with edk2-stable202208 Vincent Stehlé
2022-12-04 13:05   ` Thomas Petazzoni via buildroot [this message]
2022-12-01 18:33 ` [Buildroot] [PATCH 2/3 next] package/edk2-non-osi: new package Vincent Stehlé
2022-12-04 13:08   ` Thomas Petazzoni via buildroot
2022-12-01 18:33 ` [Buildroot] [PATCH 3/3 next] boot/edk2: bump version to edk2-stable202208 Vincent Stehlé

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=20221204140534.5f6d0539@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vincent.stehle@arm.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