From: "Denys Dmytriyenko" <denis@denix.org>
To: nm@ti.com
Cc: "meta-ti @ yoctoproject . org" <meta-ti@yoctoproject.org>,
"Bajjuri, Praneeth" <praneeth@ti.com>
Subject: Re: [meta-ti] [PATCH dunfell/dunfell-next/master 1/2] linux-ti-mainline: Bump up ti-upstream-tools SRCREV
Date: Thu, 4 Mar 2021 14:32:17 -0500 [thread overview]
Message-ID: <20210304193217.GH4892@denix.org> (raw)
In-Reply-To: <20210304042808.9389-2-nm@ti.com>
On Wed, Mar 03, 2021 at 10:28:07PM -0600, Nishanth Menon via lists.yoctoproject.org wrote:
> Bump up our recipe version for ti-upstream-tools for updates in config
> files needed for latest kernel
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
Reviewed-by: Denys Dmytriyenko <denis@denix.org>
> ---
> recipes-kernel/linux/linux-ti-mainline_git.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-kernel/linux/linux-ti-mainline_git.bb b/recipes-kernel/linux/linux-ti-mainline_git.bb
> index 6159725aa5df..b4881d0d3a40 100644
> --- a/recipes-kernel/linux/linux-ti-mainline_git.bb
> +++ b/recipes-kernel/linux/linux-ti-mainline_git.bb
> @@ -31,7 +31,7 @@ SRC_URI += " \
> file://defconfig \
> "
>
> -SRCREV_ti-upstream-tools = "3f36f66594d7905f7b97bc7870931173fd2466bd"
> +SRCREV_ti-upstream-tools = "d59b7471d99b806e3dc22342c8f42d5bb33f8cce"
> SRCREV_FORMAT = "linux"
>
> KERNEL_DEVICETREE = ""
> --
> 2.25.1.377.g2d2118b814c1
next prev parent reply other threads:[~2021-03-04 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 4:28 [PATCH dunfell/dunfell-next/master 0/2] linux-ti-mainline: Move Linux to v5.11 Nishanth Menon
2021-03-04 4:28 ` [PATCH dunfell/dunfell-next/master 1/2] linux-ti-mainline: Bump up ti-upstream-tools SRCREV Nishanth Menon
2021-03-04 19:32 ` Denys Dmytriyenko [this message]
2021-03-04 4:28 ` [PATCH dunfell/dunfell-next/master 2/2] linux-ti-mainline: Bump kernel version to v5.11 Nishanth Menon
2021-03-04 19:32 ` Denys Dmytriyenko
2021-03-04 19:30 ` [PATCH dunfell/dunfell-next/master 0/2] linux-ti-mainline: Move Linux " Denys Dmytriyenko
2021-03-04 20:55 ` 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=20210304193217.GH4892@denix.org \
--to=denis@denix.org \
--cc=meta-ti@yoctoproject.org \
--cc=nm@ti.com \
--cc=praneeth@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.