From: "zhenhua.luo@freescale.com" <zhenhua.luo@freescale.com>
To: "cristian.stoica@freescale.com" <cristian.stoica@freescale.com>,
"Otavio Salvador" <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Richard Schmitt <richard.schmitt@freescale.com>
Subject: Re: [meta-fsl-ppc][PATCH 1/4] cryptodev-linux/module: use fsl maintained source
Date: Fri, 11 Jul 2014 05:31:00 +0000 [thread overview]
Message-ID: <1365283039af4301875023b4011f63ab@CY1PR0301MB0715.namprd03.prod.outlook.com> (raw)
In-Reply-To: <2231f4d97f71483b8cffd1da02366b64@BY2PR03MB348.namprd03.prod.outlook.com>
The v2 openssl recipes were sent out to use the rebased patches, those patches are generated based on opensource openssl-1.0.1g-stable branch.
I don't see any comment on the patch series, I will merge them to ensure sec function can work in meta-fsl-ppc master.
Hopefully those FSL openssl patches can be upstreamed ASAP, we can reuse the recipes provided by poky directly. I always believe upstream is the right thing to do.
Best Regards,
Zhenhua
> -----Original Message-----
> From: meta-freescale-bounces@yoctoproject.org [mailto:meta-freescale-
> bounces@yoctoproject.org] On Behalf Of cristian.stoica@freescale.com
> Sent: Thursday, July 10, 2014 9:42 PM
> To: Otavio Salvador
> Cc: meta-freescale@yoctoproject.org; Schmitt Richard-B43082
> Subject: Re: [meta-freescale] [meta-fsl-ppc][PATCH 1/4] cryptodev-
> linux/module: use fsl maintained source
>
> > Is it possible to "rebase" the patches and include them in the recipe?
> > In case it is not and we do need a fork it is better to use
> > cryptodev-linux-fsl-ppc and cryptodev-module-fsl-ppc recipes to make
> > clear it is a fork.
> []
> I've tried a quick rebase and got back all the conflicts I already fixed
> on the merge. I'd prefer not to do them again, especially since we want
> to obsolete them with the upstream.
> If you have an alternative for the time being, then I'm OK with it.
>
> Cristian S.
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale
next prev parent reply other threads:[~2014-07-11 5:31 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
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 [this message]
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=1365283039af4301875023b4011f63ab@CY1PR0301MB0715.namprd03.prod.outlook.com \
--to=zhenhua.luo@freescale.com \
--cc=cristian.stoica@freescale.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
--cc=richard.schmitt@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.