From: "Denys Dmytriyenko" <denis@denix.org>
To: nm@ti.com
Cc: praneeth@ti.com, yogeshs@ti.com, denys@konsulko.com,
Tom Rini <trini@konsulko.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti] [dunfell/master PATCH] linux-ti-mainline: Bump kernel version to v5.13
Date: Tue, 29 Jun 2021 20:30:55 -0400 [thread overview]
Message-ID: <20210630003055.GD1528@denix.org> (raw)
In-Reply-To: <20210629233703.26088-1-nm@ti.com>
On Tue, Jun 29, 2021 at 06:37:03PM -0500, Nishanth Menon via lists.yoctoproject.org wrote:
> And lets work with the latest kernel and while at it bump the system up
> to latest ti-upstream-tools repo to get:
> * AM65x SR1.0 overlay support
> * EFI configuration to allow for the eventual support
> * Few more cleanups for new architectures that have popped in.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> recipes-kernel/linux/linux-ti-mainline_git.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/recipes-kernel/linux/linux-ti-mainline_git.bb b/recipes-kernel/linux/linux-ti-mainline_git.bb
> index 6770adcae3f7..5d043da7fee1 100644
> --- a/recipes-kernel/linux/linux-ti-mainline_git.bb
> +++ b/recipes-kernel/linux/linux-ti-mainline_git.bb
> @@ -20,9 +20,9 @@ S = "${WORKDIR}/git"
> BRANCH = "master"
> TOOLS_BRANCH = "master"
>
> -# 5.12 Mainline version
> -SRCREV = "9f4ad9e425a1d3b6a34617b8ea226d56a119a717"
> -PV = "5.12+git${SRCPV}"
> +# 5.13 Mainline version
> +SRCREV = "62fb9874f5da54fdb243003b386128037319b219"
> +PV = "5.13+git${SRCPV}"
BTW, the "+git${SRCPV}" part is to append the specific SRCREV or git SHA of
the kernel you are building to the resulting package version. That might be
useful in tracking the kernel binary on the target to a specific SHA, as well
as with binary feeds.
But if you only use official releases, you might want to drop it, as you'd
trust that SRCREV you specify for 5.13 always corresponds to the release SHA
in Linus' tree :) Just makes the package name and version much shorter...
> # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
> MACHINE_KERNEL_PR_append = "b"
> @@ -36,7 +36,7 @@ SRC_URI += " \
> file://defconfig \
> "
>
> -SRCREV_ti-upstream-tools = "d59b7471d99b806e3dc22342c8f42d5bb33f8cce"
> +SRCREV_ti-upstream-tools = "c9b8150cb00a5beb7b7f3e42d0d817aa9392fabd"
> SRCREV_FORMAT = "linux"
>
> KERNEL_DEVICETREE = ""
> --
> 2.32.0
>
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2021-06-30 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 23:37 [dunfell/master PATCH] linux-ti-mainline: Bump kernel version to v5.13 Nishanth Menon
2021-06-30 0:30 ` Denys Dmytriyenko [this message]
2021-06-30 2:11 ` [meta-ti] " Nishanth Menon
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=20210630003055.GD1528@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=trini@konsulko.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.