All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lukas Wunner" <lukas@wunner.de>
To: praneeth@ti.com
Cc: Yogesh Siraswar <yogeshs@ti.com>,
	Denys Dmytriyenko <denys@konsulko.com>,
	meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [dunfell/master PATCH] linux-ti-staging: Update 5.10 kernel to the latest commit SHA
Date: Tue, 8 Jun 2021 16:04:36 +0200	[thread overview]
Message-ID: <20210608140436.GA6013@wunner.de> (raw)
In-Reply-To: <20210608000254.12042-2-praneeth@ti.com>

On Mon, Jun 07, 2021 at 07:02:52PM -0500, praneeth via lists.yoctoproject.org wrote:
> diff --git a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
> index 4654d92d..834df5ff 100644
> --- a/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
> +++ b/recipes-kernel/linux/linux-ti-staging-rt_5.10.bb
> @@ -6,5 +6,5 @@ FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-5.10:"
>  
>  BRANCH = "ti-rt-linux-5.10.y"
>  
> -SRCREV = "afe9ba17bb94cd226f9e5dc3685e4fe32be28c5c"
> +SRCREV = "433ef931c699f08bef8c67de8458302c5f971c8b"
>  PV = "5.10.35+git${SRCPV}"
> diff --git a/recipes-kernel/linux/linux-ti-staging_5.10.bb b/recipes-kernel/linux/linux-ti-staging_5.10.bb
> index 72a6c49c..47f1669e 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 = "72d727fe733f2610e937a063bcebedce329948ec"
> +SRCREV = "ae876c7c91df646ab198331e676f250f06cfdeb5"
>  PV = "5.10.35+git${SRCPV}"
>  
>  # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild

This doesn't apply cleanly to any of the dunfell, dunfell-next nor master
branches.  SRCREV is currently 8fbd16658d11 and d85aee3e19aa, respectively
on those branches.

Which branch did you base this patch on?

Thanks,

Lukas

  reply	other threads:[~2021-06-08 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08  0:02 [dunfell/master PATCH] ti-uboot-staging: Update to the latest ti-u-boot-2021.01 praneeth
2021-06-08  0:02 ` [dunfell/master PATCH] linux-ti-staging: Update 5.10 kernel to the latest commit SHA praneeth
2021-06-08 14:04   ` Lukas Wunner [this message]
2021-06-09  0:40     ` [meta-ti] " praneeth
2021-06-09  7:19       ` Lukas Wunner
2021-06-08  0:02 ` [dunfell/master PATCH] conf: am65xx-evm: ReIntroduce display overlays for 5.10 praneeth
2021-06-08  0:05   ` praneeth
2021-06-08  0:02 ` [dunfell/master PATCH] conf/machine: am64xx: Add overlay to support icssg1-dualemac praneeth
2021-06-08  0:30 ` [meta-ti] [dunfell/master PATCH] ti-uboot-staging: Update to the latest ti-u-boot-2021.01 Denys Dmytriyenko
2021-06-08 17:01   ` praneeth

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=20210608140436.GA6013@wunner.de \
    --to=lukas@wunner.de \
    --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.