All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: Nishanth Menon <nm@ti.com>
Cc: "meta-ti @ yoctoproject . org" <meta-ti@yoctoproject.org>,
	"Bajjuri, Praneeth" <praneeth@ti.com>
Subject: Re: [PATCH dunfell/dunfell-next/master 0/2] linux-ti-mainline: Move Linux to v5.11
Date: Thu, 4 Mar 2021 14:30:09 -0500	[thread overview]
Message-ID: <20210304193009.GG4892@denix.org> (raw)
In-Reply-To: <20210304042808.9389-1-nm@ti.com>

In the subject, -next is implied. It is part of the process (and is up to 
the maintainer to follow), but you just specify the target branches you need 
this in - dunfell and master.


On Wed, Mar 03, 2021 at 10:28:06PM -0600, Nishanth Menon wrote:
> Hi,
> 
> A series of minimal patches to bump up recision to the latest kernel ->

Recision? You probably meant revision? :)


> we will need to maintain upstream-tools and kernel in sync on all
> branches involved ofcourse.
> 
> NOTE: with kernels > 5.9 (aka 5.10, 5.11...) we do have problems with
> cryptodev and kernel - we will have to try and see how best to integrate
> those as well. This is solved in master of oe-core[1] by moving to 1.12,
> however gatesgarth, dunfell are on 1.11 and 1.10 revs respectively
> which wont work since the PR integrated version is 1.12

PV, not PR.


> Nishanth Menon (2):
>   linux-ti-mainline: Bump up ti-upstream-tools SRCREV
>   linux-ti-mainline: Bump kernel version to v5.11

Ok, as long as you are not bumping linux-ti-staging, which is still the 
default kernel in meta-ti and 5.4 is being preferred, you should be fine 
with cryptodev "fix" in meta-arago.

Will need to revisit that later, if/when 5.10 LTS is ready to become the 
default in meta-ti dunfell...


>  recipes-kernel/linux/linux-ti-mainline_git.bb | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> [1] http://git.openembedded.org/openembedded-core/tree/meta/recipes-kernel/cryptodev?h=master
> [2] https://github.com/cryptodev-linux/cryptodev-linux/pull/55
> -- 
> 2.25.1.377.g2d2118b814c1
> 

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

  parent reply	other threads:[~2021-03-04 19:30 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   ` [meta-ti] " Denys Dmytriyenko
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 ` Denys Dmytriyenko [this message]
2021-03-04 20:55   ` [PATCH dunfell/dunfell-next/master 0/2] linux-ti-mainline: Move Linux " 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=20210304193009.GG4892@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.