All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ryan Eatmon" <reatmon@ti.com>
To: Yogesh Siraswar <yogeshs@ti.com>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Denys Dmytriyenko <denys@konsulko.com>,
	<meta-ti@lists.yoctoproject.org>
Subject: [meta-ti][dunfell][PATCH 1/3] linux-ti-staging: Bump to 08.02.00.001 release
Date: Mon, 7 Feb 2022 09:39:48 -0600	[thread overview]
Message-ID: <20220207153950.22274-2-reatmon@ti.com> (raw)
In-Reply-To: <20220207153950.22274-1-reatmon@ti.com>

Updated the linux version for 08.02.00.001

Signed-off-by: Ryan Eatmon <reatmon@ti.com>
---
 recipes-kernel/linux/linux-ti-staging_5.10.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
index 3f3d50af..51083382 100644
--- a/recipes-kernel/linux/linux-ti-staging_5.10.bb
+++ b/recipes-kernel/linux/linux-ti-staging_5.10.bb
@@ -23,7 +23,7 @@ S = "${WORKDIR}/git"
 
 BRANCH = "ti-linux-5.10.y"
 
-SRCREV = "dcc6bedb2c2bdb509709e4ae08303206e95ce6c2"
+SRCREV = "a523aa26d870552a44c5f48b01c3c1ea3a48751a"
 PV = "5.10.65+git${SRCPV}"
 
 # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
-- 
2.17.1


  reply	other threads:[~2022-02-07 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 15:39 [meta-ti][dunfell][PATCH 0/3] Update to 08.02.00.001 Ryan Eatmon
2022-02-07 15:39 ` Ryan Eatmon [this message]
2022-02-11  3:41   ` [meta-ti][dunfell][PATCH 1/3] linux-ti-staging: Bump to 08.02.00.001 release Denys Dmytriyenko
2022-02-11 12:40     ` Ryan Eatmon
2022-02-07 15:39 ` [meta-ti][dunfell][PATCH 2/3] linux-ti-staging-rt: " Ryan Eatmon
2022-02-07 15:39 ` [meta-ti][dunfell][PATCH 3/3] u-boot-ti-staging: " Ryan Eatmon

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=20220207153950.22274-2-reatmon@ti.com \
    --to=reatmon@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=praneeth@ti.com \
    --cc=yogeshs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.