From: Marek Vasut <marex@denx.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: lftan@altera.com, waltergoossens@home.nl,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 5/8] openssl: Add nios2 configuration
Date: Tue, 22 Sep 2015 02:06:52 +0200 [thread overview]
Message-ID: <201509220206.52454.marex@denx.de> (raw)
In-Reply-To: <CAJTo0LbcO+Wz8=GwYKbM+6WiVaeOVqZo6iPo+gpErg1V0NH_LQ@mail.gmail.com>
On Monday, September 21, 2015 at 02:38:52 PM, Burton, Ross wrote:
> On 21 September 2015 at 11:49, Marek Vasut <marex@denx.de> wrote:
> > This approach [1] is applicable to nios2 just fine, so I'll go with the
> > same. Can the rest of the patches here be applied, so I don't have to
> > repost them please ?
>
> Absolutely, the rest of the series is queued in ross/mut already.
Thanks! I just sent the OpenSSL patch in reply to this mail, it's build
tested too.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2015-09-22 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 22:43 [PATCH 0/8] nios2 fixes Marek Vasut
2015-09-19 22:43 ` [PATCH 1/8] insane: Add nios2 support Marek Vasut
2015-09-19 22:43 ` [PATCH 2/8] siteinfo: Add nios2-linux Marek Vasut
2015-09-19 22:43 ` [PATCH 3/8] kernel-arch: Add nios2 to valid archs Marek Vasut
2015-09-19 22:43 ` [PATCH 4/8] linux-yocto: depend on libgcc for nios2 Marek Vasut
2015-09-19 22:43 ` [PATCH 5/8] openssl: Add nios2 configuration Marek Vasut
2015-09-21 10:35 ` Burton, Ross
2015-09-21 10:49 ` Marek Vasut
2015-09-21 12:38 ` Burton, Ross
2015-09-22 0:05 ` [PATCH] openssl: Add mapping for nios2 Marek Vasut
2015-09-22 0:06 ` Marek Vasut [this message]
2015-09-19 22:43 ` [PATCH 6/8] libtool: Fix nios2 support Marek Vasut
2015-09-19 22:43 ` [PATCH 7/8] pixman: Fix missing FE_DIVBYZERO on nios2 Marek Vasut
2015-09-19 22:43 ` [PATCH 8/8] libgpg-error: Add support for nios2 Marek Vasut
2015-09-20 11:59 ` [PATCH 0/8] nios2 fixes Philip Balister
2015-09-21 1:07 ` Marek Vasut
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=201509220206.52454.marex@denx.de \
--to=marex@denx.de \
--cc=lftan@altera.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=waltergoossens@home.nl \
/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