Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Replace ocf-linux with cryptodev-linux
Date: Mon, 31 Mar 2014 11:02:16 +0800	[thread overview]
Message-ID: <5338DAB8.3070606@windriver.com> (raw)
In-Reply-To: <1396000238.24890.171.camel@ted>

On 2014年03月28日 17:50, Richard Purdie wrote:
> On Wed, 2014-03-26 at 18:15 +0800, Kai Kang wrote:
>> Replace ocf-linux with cryptodev-linux because linux-yocto use cryptodev-linux to implement /dev/crypto.
>>
>> Build for qemux86 and qemuarm. Test on qemux86.
> This did break the build:
>
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=8c3eb5ee4582b6f6d489549290937657f37fc19e
>
> however I've fixed it.

Thanks, RP.

-- Kai

>
> Cheers,
>
> Richard
>
>
>


-- 
Regards,
Neil | Kai Kang



      reply	other threads:[~2014-03-31  3:02 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
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 [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=5338DAB8.3070606@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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