From: "Khem Raj" <raj.khem@gmail.com>
To: Denys Dmytriyenko <denis@denix.org>,
openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@ti.com>
Subject: Re: [OE-core] [PATCH] cryptodev: bump 1 commit past 1.11 to fix 5.9-rc1+
Date: Wed, 9 Sep 2020 17:24:05 -0700 [thread overview]
Message-ID: <a1c03ca8-5c09-ee52-7912-42c560ca689c@gmail.com> (raw)
In-Reply-To: <1599688063-38109-1-git-send-email-denis@denix.org>
On 9/9/20 2:47 PM, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@ti.com>
>
> There's one commit on top of 1.11 release that fixes builds against kernel 5.9-rc1+.
since we call the recipe as 1.11, perhaps its better to explcitly apply
this patch via SRC_URI or alter PV to reflect this SRCREV changes,
>
> Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> ---
> meta/recipes-kernel/cryptodev/cryptodev.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/cryptodev/cryptodev.inc b/meta/recipes-kernel/cryptodev/cryptodev.inc
> index 906f4fc..c050eda 100644
> --- a/meta/recipes-kernel/cryptodev/cryptodev.inc
> +++ b/meta/recipes-kernel/cryptodev/cryptodev.inc
> @@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
> SRC_URI = "git://github.com/cryptodev-linux/cryptodev-linux \
> "
> -SRCREV = "2299d39475e91392abd050ea09f2d20feecb4adf"
> +SRCREV = "fabe5989a3dc9fba0cd0a40b612247cdde351c01"
>
> S = "${WORKDIR}/git"
>
>
>
>
>
next prev parent reply other threads:[~2020-09-10 0:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 21:47 [PATCH] cryptodev: bump 1 commit past 1.11 to fix 5.9-rc1+ Denys Dmytriyenko
2020-09-10 0:24 ` Khem Raj [this message]
2020-09-10 0:38 ` [OE-core] " Denys Dmytriyenko
2020-09-10 0:46 ` Khem Raj
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=a1c03ca8-5c09-ee52-7912-42c560ca689c@gmail.com \
--to=raj.khem@gmail.com \
--cc=denis@denix.org \
--cc=denys@ti.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox