From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] linux-yocto/6.6: pull request
Date: Fri, 28 Jun 2024 13:56:12 -0400 [thread overview]
Message-ID: <cover.1719597265.git.bruce.ashfield@gmail.com> (raw)
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Richard,
Here are the gathered -stable updates, and the AMD cpu traceback "fix".
You can see the details in the patch for the traceback how I decided top
solve it (for now).
Cheers,
Bruce
The following changes since commit 058465859ed5a62997bb9424e8eb88b543f43a86:
xz: Update LICENSE variable for xz packages (2024-06-27 13:03:35 +0100)
are available in the Git repository at:
https://git.yoctoproject.org/poky-contrib zedd/kernel
https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (3):
linux-yocto/6.6: update to v6.6.34
linux-yocto/6.6: update to v6.6.35
linux-yocto/6.6: fix AMD boot trace
.../linux/linux-yocto-rt_6.6.bb | 6 ++--
.../linux/linux-yocto-tiny_6.6.bb | 6 ++--
meta/recipes-kernel/linux/linux-yocto_6.6.bb | 28 +++++++++----------
3 files changed, 20 insertions(+), 20 deletions(-)
--
2.39.2
next reply other threads:[~2024-06-28 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 17:56 bruce.ashfield [this message]
2024-06-28 17:56 ` [PATCH 1/3] linux-yocto/6.6: update to v6.6.34 bruce.ashfield
2024-06-28 17:56 ` [PATCH 2/3] linux-yocto/6.6: update to v6.6.35 bruce.ashfield
2024-06-28 17:56 ` [PATCH 3/3] linux-yocto/6.6: fix AMD boot trace bruce.ashfield
-- strict thread matches above, loose matches on Subject: below --
2024-02-16 20:05 [PATCH 0/3] linux-yocto/6.6: pull request bruce.ashfield
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=cover.1719597265.git.bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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