From: Paul Eggleton <paul.eggleton@intel.com>
To: openembedded-core@lists.openembedded.org
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
"Wold, Saul" <saul.wold@intel.com>,
"Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] dropbear: a fix for hang in dropbearkey, built for x32
Date: Tue, 28 May 2013 17:15:08 +0100 [thread overview]
Message-ID: <2106642.Q9pyc3AhWP@helios> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C70406D1D@ORSMSX103.amr.corp.intel.com>
On Tuesday 28 May 2013 16:10:33 Kamble, Nitin A wrote:
> Saul, RP,
> FYI, this fix is still pending for oecore layer.
It has already been merged:
http://cgit.openembedded.org/openembedded-core/commit/?id=8f5bc47729edb8cb051d81e9ff1680cb8d2eca25
> Paul,
> This is for the 1.4.1 bug
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4496 . Once Saul or RP
> pulls it in master, you can pull it in 1.4.1 release branch.
OK; I have done this locally.
Cheers,
Paul
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2013-05-28 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 16:09 [PATCH 0/1] a x32 fix for dropbear hang nitin.a.kamble
2013-05-23 16:09 ` [PATCH 1/1] dropbear: a fix for hang in dropbearkey, built for x32 nitin.a.kamble
2013-05-28 16:10 ` Kamble, Nitin A
2013-05-28 16:15 ` Paul Eggleton [this message]
2013-05-28 16:25 ` Kamble, Nitin A
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=2106642.Q9pyc3AhWP@helios \
--to=paul.eggleton@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.com \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox