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][master][PATCH 4/4] linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202311060100
Date: Mon, 6 Nov 2023 06:47:58 -0600 [thread overview]
Message-ID: <1699274878-149529-5-git-send-email-lcpdbld@list.ti.com> (raw)
In-Reply-To: <1699274878-149529-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_6.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
index 55407cb..d8e44d7 100644
--- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
+++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
@@ -23,7 +23,7 @@ S = "${WORKDIR}/git"
BRANCH ?= "ti-linux-6.1.y"
-SRCREV ?= "37f154cc9ceeee52ff63ffbe8b44d295a1fc708b"
+SRCREV ?= "7d494fe58c8e5d41a6bd886c9a628a7fff5763f9"
PV = "6.1.46+git${SRCPV}"
# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
1.8.3.1
prev parent reply other threads:[~2023-11-06 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 12:47 [meta-ti][master][PATCH 0/4] Update to cicd.master.202311060100 LCPD Automation Script
2023-11-06 12:47 ` [meta-ti][master][PATCH 1/4] ti-linux-fw: CI/CD Auto-Merger: cicd.master.202311060100 LCPD Automation Script
2023-11-06 12:47 ` [meta-ti][master][PATCH 2/4] u-boot-ti-staging_2023.04: " LCPD Automation Script
2023-11-06 12:47 ` [meta-ti][master][PATCH 3/4] linux-ti-staging-rt_6.1: " LCPD Automation Script
2023-11-06 12:47 ` LCPD Automation Script [this message]
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=1699274878-149529-5-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).