Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Martin Jansa <martin.jansa@gmail.com>,
	Joshua Lock <joshua.g.lock@intel.com>,
	Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [fido][PATCH 0/1] Undo ABI breakage in OpenSSL
Date: Fri, 13 May 2016 16:50:44 -0700	[thread overview]
Message-ID: <57366854.8060203@gmail.com> (raw)
In-Reply-To: <1463157281.9746.114.camel@linuxfoundation.org>



On 05/13/2016 09:34 AM, Richard Purdie wrote:
> On Thu, 2016-05-12 at 16:16 +0200, Martin Jansa wrote:
>> On Thu, May 12, 2016 at 01:06:33PM +0100, Joshua Lock wrote:
>>> The backported upgrade to OpenSSL 1.0.2h introduced a newer version
>>> of
>>> Debian's linker version-script which breaks the OpenSSL ABI.
>>> This isn't desirable for a stable release, thus the attached patch
>>> reverts
>>> the linker-version changes and simply adds the 2 new symbols
>>> required by
>>> 1.0.2h.
>>>
>>> Thanks to Martin Jansa for spotting the issue and suggesting a fix.
>>
>> Thanks for following it and getting it merged so quickly.
>>
>> It was already merged in fido, can we get the same to jethro (which
>> was
>> also recently upgraded to 1.0.2h)?
> 
> I'm hoping someone will give me a patch series which does this
> correctly for jethro. Its why I haven't taken the previous pull
> request.
> 

sent
- armin

> Cheers,
> 
> Richard
> 
> 
> 


      parent reply	other threads:[~2016-05-13 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-12 12:06 [fido][PATCH 0/1] Undo ABI breakage in OpenSSL Joshua Lock
     [not found] ` <cover.1463054731.git.joshua.g.lock@intel.com>
2016-05-12 12:06   ` [fido][PATCH 1/1] openssl: prevent ABI break from earlier fido releases Joshua Lock
2016-05-12 14:16 ` [fido][PATCH 0/1] Undo ABI breakage in OpenSSL Martin Jansa
2016-05-13 16:34   ` Richard Purdie
2016-05-13 20:59     ` akuster808
2016-05-13 23:50     ` akuster808 [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=57366854.8060203@gmail.com \
    --to=akuster808@gmail.com \
    --cc=joshua.g.lock@intel.com \
    --cc=liezhi.yang@windriver.com \
    --cc=martin.jansa@gmail.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