From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mikko Rapeli <mikko.rapeli@linaro.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 4/4] linux-yocto: use openssl-native.bbclass
Date: Tue, 04 Oct 2022 11:44:51 +0100 [thread overview]
Message-ID: <e0fc2054236524ba2cca50068503089aaaf72c08.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221004101107.2745139-1-mikko.rapeli@linaro.org>
On Tue, 2022-10-04 at 13:11 +0300, Mikko Rapeli wrote:
> It sets environment variables etc correctly for openssl-native use.
> For most kernel side use cases are covered by plain openssl native
> wrapper but some out of tree e.g. python scripts may be not.
When you say "out of tree", you mean scripts in the kernel we don't use
by default, or scripts that aren't in the kernel at all but some users
add?
I'd have thought the dependency on the class would be added where it
was being used?
Cheers,
Richard
next prev parent reply other threads:[~2022-10-04 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 10:11 [PATCH 4/4] linux-yocto: use openssl-native.bbclass Mikko Rapeli
2022-10-04 10:44 ` Richard Purdie [this message]
2022-10-04 11:28 ` [OE-core] " Mikko Rapeli
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=e0fc2054236524ba2cca50068503089aaaf72c08.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mikko.rapeli@linaro.org \
--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