From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openssl-1.0.0d: use openssl.inc from meta-oe
Date: Tue, 16 Aug 2011 07:45:36 -0700 [thread overview]
Message-ID: <4E4A8290.207@gmail.com> (raw)
In-Reply-To: <1313500918-26444-1-git-send-email-Martin.Jansa@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/16/2011 06:21 AM, Martin JaMa Jansa wrote:
> * full path was using openssl.inc from oe-core which doesn't have
> BBCLASSEXTEND and INC_PR
>
> Signed-off-by: Martin JaMa Jansa <Martin.Jansa@gmail.com>
Acked-by: Khem Raj <raj.khem@gmail.com>
> --- .../recipes-connectivity/openssl/openssl_1.0.0d.bb | 2 +- 1
> files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta-oe/recipes-connectivity/openssl/openssl_1.0.0d.bb
> b/meta-oe/recipes-connectivity/openssl/openssl_1.0.0d.bb index
> cd5408d..73c8df5 100644 ---
> a/meta-oe/recipes-connectivity/openssl/openssl_1.0.0d.bb +++
> b/meta-oe/recipes-connectivity/openssl/openssl_1.0.0d.bb @@ -1,4 +1,4
> @@ -require recipes-connectivity/openssl/openssl.inc +require
> openssl.inc
that leaked from patch I am trying to convert meta-oe recipes into bbappend.
>
> # For target side versions of openssl enable support for OCF Linux
> driver # if they are available.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk5Kgo8ACgkQuwUzVZGdMxS34ACfXmywmrEmY9MCg2Vrt18KY60p
lWEAn0AiFozJ4Qf8liEMRuLHeLTVlU1g
=tc+e
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-08-16 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 13:21 [PATCH] openssl-1.0.0d: use openssl.inc from meta-oe Martin JaMa Jansa
2011-08-16 14:45 ` Khem Raj [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=4E4A8290.207@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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