From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] glib-2.0: fix makefiles
Date: Thu, 14 Jul 2011 15:09:31 +0100 [thread overview]
Message-ID: <1310652571.20015.1157.camel@rex> (raw)
In-Reply-To: <c8ed5900d3ef67a57db6d0b50226269f1c25477e.1310561877.git.nitin.a.kamble@intel.com>
On Wed, 2011-07-13 at 05:59 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> x32 exposed this bug in the makefiles.
Nitin, could you perhaps document what the bug actually is? :) I can
guess but the patch header should really give a little more info.
Also, does this address some LDFLAGS QA warnings by any chance?
Cheers,
Richard
next prev parent reply other threads:[~2011-07-14 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 12:59 [PATCH 0/3] Misc fixes related to x32 nitin.a.kamble
2011-07-13 12:59 ` [PATCH 1/3] bitbake.conf, bbclasses: define *_LD_ARCH & *AS_ARCH vars nitin.a.kamble
2011-07-13 21:12 ` Khem Raj
2011-07-13 12:59 ` [PATCH 2/3] glib-2.0: fix makefiles nitin.a.kamble
2011-07-14 14:09 ` Richard Purdie [this message]
2011-07-13 12:59 ` [PATCH 3/3] openssl: compilation fixes for x32 nitin.a.kamble
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=1310652571.20015.1157.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 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.