From: LCPD Automation Script <lcpdbld@list.ti.com>
To: Ryan Eatmon <reatmon@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
<meta-ti@lists.yoctoproject.org>
Subject: [meta-ti][kirkstone][PATCH 3/4] linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.kirkstone.202311161200
Date: Thu, 16 Nov 2023 15:29:46 -0600 [thread overview]
Message-ID: <1700170187-132967-4-git-send-email-lcpdbld@list.ti.com> (raw)
In-Reply-To: <1700170187-132967-1-git-send-email-lcpdbld@list.ti.com>
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
index d828f2b..3c82270 100644
--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
@@ -6,7 +6,7 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.1:"
BRANCH = "ti-rt-linux-6.1.y"
-SRCREV = "a98195cd9fc9813d8a2c9959484e5d3f9eb2502e"
+SRCREV = "2f5db0e70b5e1ea128754128ff87560ff0c7ffbb"
include ${@ 'recipes-kernel/linux/ti-extras-rt.inc' if d.getVar('TI_EXTRAS') else ''}
--
1.8.3.1
next prev parent reply other threads:[~2023-11-16 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 21:29 [meta-ti][kirkstone][PATCH 0/4] Update to cicd.kirkstone.202311161200 LCPD Automation Script
2023-11-16 21:29 ` [meta-ti][kirkstone][PATCH 1/4] ti-linux-fw: CI/CD Auto-Merger: cicd.kirkstone.202311161200 LCPD Automation Script
2023-11-16 21:29 ` [meta-ti][kirkstone][PATCH 2/4] u-boot-ti-staging_2023.04: " LCPD Automation Script
2023-11-16 21:29 ` LCPD Automation Script [this message]
2023-11-16 21:29 ` [meta-ti][kirkstone][PATCH 4/4] linux-ti-staging_6.1: " LCPD Automation Script
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=1700170187-132967-4-git-send-email-lcpdbld@list.ti.com \
--to=lcpdbld@list.ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.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).