From: Randy MacLeod <randy.macleod@windriver.com>
To: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe][meta-oe][PATCH] pkcs11-helper: 1.11 -> 1.22
Date: Tue, 10 Apr 2018 15:39:24 -0400 [thread overview]
Message-ID: <84ab73de-b18d-caec-c9cc-2a48e1385faf@windriver.com> (raw)
In-Reply-To: <1520848583-21222-1-git-send-email-huangqy.fnst@cn.fujitsu.com>
On 2018-03-12 05:56 AM, Huang Qiyu wrote:
> Upgrade pkcs11-helper from 1.11 to 1.22.
>
> Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
> ---
> .../pkcs11-helper/{pkcs11-helper_1.11.bb => pkcs11-helper_1.22.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta-oe/recipes-crypto/pkcs11-helper/{pkcs11-helper_1.11.bb => pkcs11-helper_1.22.bb} (95%)
Huang,
Wrong list, send to:
openembedded-devel@lists.openembedded.org
Thanks,
../Randy
>
> diff --git a/meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.11.bb b/meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.22.bb
> similarity index 95%
> rename from meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.11.bb
> rename to meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.22.bb
> index db71bd0..51ccf37 100644
> --- a/meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.11.bb
> +++ b/meta-oe/recipes-crypto/pkcs11-helper/pkcs11-helper_1.22.bb
> @@ -20,7 +20,7 @@ SRC_URI[md5sum] = "9f62af9f475901b89355266141306673"
> SRC_URI[sha256sum] = "494ec59c93e7c56c528f335d9353849e2e7c94a6b1b41c89604694e738113386"
>
> S = "${WORKDIR}/git"
> -SRCREV = "e7adf8f35be232a4f04c53b4ac409be52792093e"
> +SRCREV = "a6e54e9bdd57dd4e98a2fbf984fe7fe4a9d60171"
>
> DEPENDS = "zlib nettle gnutls gmp openssl nss nspr"
>
>
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2018-04-10 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 9:56 [oe][meta-oe][PATCH] pkcs11-helper: 1.11 -> 1.22 Huang Qiyu
2018-03-12 10:02 ` ✗ patchtest: failure for " Patchwork
2018-04-10 19:39 ` Randy MacLeod [this message]
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=84ab73de-b18d-caec-c9cc-2a48e1385faf@windriver.com \
--to=randy.macleod@windriver.com \
--cc=huangqy.fnst@cn.fujitsu.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