All of lore.kernel.org
 help / color / mirror / Atom feed
From: "cristian.stoica@freescale.com" <cristian.stoica@freescale.com>
To: "ting.liu@freescale.com" <ting.liu@freescale.com>,
	Otavio Salvador <otavio@ossystems.com.br>,
	Richard Schmitt <richard.schmitt@freescale.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-ppc][PATCH 1/4] cryptodev-linux/module: use fsl maintained source
Date: Thu, 10 Jul 2014 07:15:35 +0000	[thread overview]
Message-ID: <b9f408c7eff5444182e5a31afff8a0ed@BY2PR03MB348.namprd03.prod.outlook.com> (raw)
In-Reply-To: <b58db15226ff437f857e4919c80663a9@BLUPR03MB151.namprd03.prod.outlook.com>

Hi Ting,

> I tried to rebase our internal cryptodev-linux and openssl onto upstream
> but met lots of merge failures.
> Could you please help to identify what is still pending to be upstreamed,
> as Otavio said.

[CS] cryptodev-linux from sdk-v1.6 tree has the merge conflicts already fixed. Please check commit ID c9baf0623bdc55e8adfc91bf675e8148826d57d1.

We're currently working with Phil Sutter from cryptodev to upstream our patches. As the modifications involve some API changes, the process is relatively  slow but steady. Our plan is to make minimum modifications to cryptodev internals so the rest of patches are easy to integrate.

Cristian S.

  reply	other threads:[~2014-07-10  7:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  8:16 [meta-fsl-ppc][PATCH 1/4] cryptodev-linux/module: use fsl maintained source ting.liu
2014-07-09  8:16 ` [meta-fsl-ppc][PATCH 2/4] openssl: downgrade to 1.0.1g ting.liu
2014-07-09  8:16 ` [meta-fsl-ppc][PATCH 3/4] openssl: set preferred version " ting.liu
2014-07-09  8:16 ` [meta-fsl-ppc][PATCH 4/4] openssl: use fsl maintained source ting.liu
2014-07-09  8:32   ` Redwan Mohamed
2014-07-10  2:28     ` ting.liu
2014-07-09 17:24   ` Otavio Salvador
2014-07-09 17:28 ` [meta-fsl-ppc][PATCH 1/4] cryptodev-linux/module: " Otavio Salvador
2014-07-10  1:46   ` ting.liu
2014-07-10  6:51   ` ting.liu
2014-07-10  7:15     ` cristian.stoica [this message]
2014-07-10 10:34       ` ting.liu
2014-07-10 12:19       ` Otavio Salvador
2014-07-10 13:41         ` cristian.stoica
2014-07-11  5:31           ` zhenhua.luo
2014-07-09 20:19 ` Bob Cochran
2014-07-10  2:13   ` ting.liu
2014-07-11 14:41     ` Bob Cochran
2014-07-11 15:40       ` ting.liu
2014-07-15  3:33         ` Bob Cochran
2014-07-15  5:14           ` ting.liu

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=b9f408c7eff5444182e5a31afff8a0ed@BY2PR03MB348.namprd03.prod.outlook.com \
    --to=cristian.stoica@freescale.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=richard.schmitt@freescale.com \
    --cc=ting.liu@freescale.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.