From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Henry Wang <Henry.Wang@arm.com>
Cc: meta-virtualization@lists.yoctoproject.org,
Wei Chen <wei.chen@arm.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Diego Sueiro <diego.sueiro@arm.com>,
Christopher Clark <christopher.w.clark@gmail.com>
Subject: Re: [mickledore][PATCH 0/2] Use linux-yocto 6.1 for RPi4 in mickledore
Date: Wed, 5 Jul 2023 23:55:15 -0400 [thread overview]
Message-ID: <ZKY7I4884rY7gO6u@gmail.com> (raw)
In-Reply-To: <20230704112952.721002-1-Henry.Wang@arm.com>
In message: [mickledore][PATCH 0/2] Use linux-yocto 6.1 for RPi4 in mickledore
on 04/07/2023 Henry Wang wrote:
> This series is the original commits on master branch rebased on top
> of mickledore. Sending to mickledore to make the RPi4 use linux-yocto 6.1.
The changes look ok to me, but for mickledore, there's no reason
to drop the 5.15 bbappend, we only removed it in master due to
gcc-13 issues, it is still a valid kernel target in mickledore.
So I've merged all but the bbappend drop.
Bruce
>
> I've verified latest Xen hypervisor with these patches can boot
> linux-yocto 6.1 as Dom0 and all our internal Xen test cases passed.
>
> Christopher Clark (1):
> rpi, xen, linux-yocto: enable linux-yocto 6.1 for RPi4
>
> Martin Jansa (1):
> rpi: linux-yocto: drop 5.15 bbappend
>
> .../{linux-yocto_5.15.bbappend => linux-yocto_6.1.bbappend} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename dynamic-layers/raspberrypi/recipes-kernel/linux/{linux-yocto_5.15.bbappend => linux-yocto_6.1.bbappend} (51%)
>
> --
> 2.25.1
>
next parent reply other threads:[~2023-07-06 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230704112952.721002-1-Henry.Wang@arm.com>
2023-07-06 3:55 ` Bruce Ashfield [this message]
2023-07-06 4:04 ` [meta-virtualization] [mickledore][PATCH 0/2] Use linux-yocto 6.1 for RPi4 in mickledore Henry Wang
2023-07-04 11:35 Henry Wang
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=ZKY7I4884rY7gO6u@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=Henry.Wang@arm.com \
--cc=bertrand.marquis@arm.com \
--cc=christopher.w.clark@gmail.com \
--cc=diego.sueiro@arm.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=wei.chen@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).