From: Kang Kai <Kai.Kang@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Replace ocf-linux with cryptodev-linux
Date: Fri, 28 Mar 2014 11:03:54 +0800 [thread overview]
Message-ID: <5334E69A.90200@windriver.com> (raw)
In-Reply-To: <CAP9ODKpRZXUxM=QGOBR4xmh=vBWBd6VOqYK0AZwvon_MG4pQGA@mail.gmail.com>
On 2014年03月26日 22:42, Otavio Salvador wrote:
> Hello Kai,
>
> On Wed, Mar 26, 2014 at 7:15 AM, Kai Kang <kai.kang@windriver.com> wrote:
>> Replace ocf-linux with cryptodev-linux because linux-yocto use cryptodev-linux to implement /dev/crypto.
> Thanks for handling it; I was going to address same issue this week so
> we could have it upstreamed and drop the Freescale bbappends for it.
> This indeed makes my life easier :-) So thank you :-)
>
Hi Otavio,
It is my pleasure if it could help. :)
--
Regards,
Neil | Kai Kang
next prev parent reply other threads:[~2014-03-28 3:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 10:15 [PATCH 0/3] Replace ocf-linux with cryptodev-linux Kai Kang
2014-03-26 10:15 ` [PATCH 1/3] cryptodev-linux: add recipe Kai Kang
2014-03-26 14:40 ` Otavio Salvador
2014-03-28 17:11 ` Denys Dmytriyenko
2014-03-26 10:15 ` [PATCH 2/3] openssl: replace dependency ocf-linux with cryptodev-linux Kai Kang
2014-03-26 10:15 ` [PATCH 3/3] ocf-linux: remove recipe Kai Kang
2014-03-26 14:42 ` [PATCH 0/3] Replace ocf-linux with cryptodev-linux Otavio Salvador
2014-03-28 3:03 ` Kang Kai [this message]
2014-03-28 17:13 ` Denys Dmytriyenko
2014-03-28 17:18 ` Bruce Ashfield
2014-03-28 17:34 ` Denys Dmytriyenko
2014-03-28 17:42 ` Bruce Ashfield
2014-03-28 17:22 ` Richard Purdie
2014-03-28 17:37 ` Denys Dmytriyenko
2014-03-28 9:50 ` Richard Purdie
2014-03-31 3:02 ` Kang Kai
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=5334E69A.90200@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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