From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Fix elfutils-native with GCC 4.6
Date: Wed, 06 Apr 2011 08:03:48 -0700 [thread overview]
Message-ID: <1302102228.22904.69.camel@rex> (raw)
In-Reply-To: <cover.1302087686.git.josh@linux.intel.com>
On Wed, 2011-04-06 at 12:10 +0100, Joshua Lock wrote:
> From: Joshua Lock <josh@linux.intel.com>
>
> Unfortunately I'm currently unable to test this on a machine with GCC version
> other than 4.6 but thought it was worth getting this patch out there as I'll
> be in the air and travelling until next week.
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
> Branch: josh/elfutils
> Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/elfutils
>
> Thanks,
> Joshua Lock <josh@linux.intel.com>
> ---
>
>
> Joshua Lock (1):
> elfutils: remove unused variables to fix compilation with GCC 4.6
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-04-06 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 11:10 [PATCH 0/1] Fix elfutils-native with GCC 4.6 Joshua Lock
2011-04-06 11:10 ` [PATCH 1/1] elfutils: remove unused variables to fix compilation " Joshua Lock
2011-04-06 15:03 ` Richard Purdie [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=1302102228.22904.69.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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