From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Chris Larson <kergoth@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Random fixes from the Mentor Graphics push queue
Date: Tue, 3 Dec 2013 21:38:12 -0500 [thread overview]
Message-ID: <529E9594.3020201@windriver.com> (raw)
In-Reply-To: <1386110407.4463.148.camel@ted>
On 12/3/2013, 5:40 PM, Richard Purdie wrote:
> On Tue, 2013-12-03 at 11:40 -0700, Chris Larson wrote:
>> On Wed, Nov 27, 2013 at 11:07 AM, Christopher Larson
>> <kergoth@gmail.com> wrote:
>> The following changes since commit
>> f991d2d60b74f5ebd990f77aecd3324b1a4533e9:
>>
>> libpng: set reasonable SUMMARY (2013-11-27 11:51:08 +0000)
>>
>> are available in the git repository at:
>>
>> https://github.com/kergoth/oe-core.git random-fixes
>> https://github.com/kergoth/oe-core/tree/random-fixes
>>
>> Christopher Larson (7):
>> update-rc.d: process symlinks recursively
>> perf: remove /usr/local/include from default makefile
>> includes
>> pulseaudio: fix RDEPENDS traversal for consolekit
>>
>> Were there issues with these, or was it just that further testing was
>> necessary? I noticed this series was partially applied.
>
> On the most part just being cautious for M1.
>
> The perf one does worry me as we keep going around in circles on it
> where we change one thing, it breaks something else, we fix that,
> something else breaks, we fix that and we end up back where we started.
> The commit history and/or the mailing list should have details about
> what happened there. CC'ing Bruce since I know he has opinions on the
> perf fix. Bruce, did we get a fix for that upstream in the end?
My favourite topic. I'm working on the upstream fix, which was that we
shouldn't be using CFLAGS and LDFLAGS to pass build values into perf,
but instead use EXTRA_CLFAGS (which exists) and EXTRA_LDFLAGS (Which
doesn't exist yet, and that's the patch I have queued).
Looking at Chris' posted patch, I can't actually tell what it was
fixing, since INCLUDES isn't directly used by the perf Makefiles and on
a really quick check, I can't see what CONFIG_INCLUDES is set to either.
I'm sure I'm just being dense (long day) and I'm missing something, so
I can't map the short log's intent to what the patch is actually doing.
The patch won't undo anything that we are working to fix/change
upstream, but since something is whizzing over my head, I can't be sure
about side effects.
Cheers,
Bruce
>
> Cheers,
>
> Richard
>
>
>
>
next prev parent reply other threads:[~2013-12-04 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 18:07 Random fixes from the Mentor Graphics push queue Christopher Larson
2013-11-27 18:07 ` [PATCH 1/7] update-rc.d: process symlinks recursively Christopher Larson
2013-11-27 18:07 ` [PATCH 2/7] quota: apply patch to obey tcp-wrappers config Christopher Larson
2013-11-27 18:07 ` [PATCH 3/7] python, python-native: fix PARALLEL_MAKEINST failure Christopher Larson
2013-11-27 18:07 ` [PATCH 4/7] cairo: add/use packageconfig for valgrind support Christopher Larson
2013-11-27 18:07 ` [PATCH 5/7] perf: remove /usr/local/include from default makefile includes Christopher Larson
2013-11-27 18:07 ` [PATCH 6/7] qemu: handle CLOEXEC/NONBLOCK if unavailable on host Christopher Larson
2013-11-27 18:07 ` [PATCH 7/7] pulseaudio: fix RDEPENDS traversal for consolekit Christopher Larson
2013-12-11 21:22 ` Martin Jansa
2013-12-12 22:55 ` Chris Larson
2013-12-03 18:40 ` Random fixes from the Mentor Graphics push queue Chris Larson
2013-12-03 22:40 ` Richard Purdie
2013-12-04 2:38 ` Bruce Ashfield [this message]
2013-12-04 2:42 ` Chris Larson
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=529E9594.3020201@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=kergoth@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