From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from vms173017pub.verizon.net (vms173017pub.verizon.net [206.46.173.17]) by mail.openembedded.org (Postfix) with ESMTP id A591B6C735 for ; Fri, 28 Mar 2014 17:37:13 +0000 (UTC) Received: from gandalf.denix.org ([unknown] [71.191.205.189]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0N3500E1DQ9RST40@vms173017.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Fri, 28 Mar 2014 12:37:04 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 9578C20398; Fri, 28 Mar 2014 13:37:03 -0400 (EDT) Date: Fri, 28 Mar 2014 13:37:03 -0400 From: Denys Dmytriyenko To: Richard Purdie Message-id: <20140328173703.GL3370@denix.org> References: <20140328171338.GI3370@denix.org> <1396027334.14790.11.camel@ted> MIME-version: 1.0 In-reply-to: <1396027334.14790.11.camel@ted> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Otavio Salvador , Patches and discussions about the oe-core layer Subject: Re: [PATCH 0/3] Replace ocf-linux with cryptodev-linux X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 17:37:13 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Fri, Mar 28, 2014 at 05:22:14PM +0000, Richard Purdie wrote: > On Fri, 2014-03-28 at 13:13 -0400, Denys Dmytriyenko wrote: > > On Wed, Mar 26, 2014 at 11:42:39AM -0300, Otavio Salvador wrote: > > > Hello Kai, > > > > > > On Wed, Mar 26, 2014 at 7:15 AM, Kai Kang 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. > > > > So, we also have a recipe of cryptodev for TI builds. But it's not just a > > header file and we need the actual module to be built and packaged... > > > > I'm rather surprised it was merged so quickly w/o further discussion... :( > > From my perspective, the ocf version looked dead and I had several > people saying this was the right thing to do with nobody saying > otherwise, both here on list and in some conversations I had with > people. With the release approaching, it was kind of late to do it > equally, it did appear to be the right thing to switch to so I got on > and tested and then merged it. > > I don't consider things "set in stone", I think we can build upon this > incrementally. Thanks. I'll try to work an incremental solution, then, so it works for us and doesn't break other use cases - please see my reply to Bruce. -- Denys