From: Chris Ferron <chris.e.ferron at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH 1/2] Make it possible to include parse-events.h before libc headers.
Date: Thu, 26 Jul 2012 15:09:49 -0700 [thread overview]
Message-ID: <5011C02D.80805@linux.intel.com> (raw)
In-Reply-To: 1343244370.6440.4.camel@sara
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On 07/25/2012 12:26 PM, Magnus Fromreide wrote:
> On Wed, 2012-07-25 at 10:44 -0700, Chris Ferron wrote:
>> On 07/23/2012 11:03 PM, Magnus Fromreide wrote:
>>> The __unused macro interferes with the glibc and is in a reserved namespace
>>> so it should be renamed.
>>> Additionally the __ununsed macro is used from just one implementation file so
>>> the macro is moved there.
>>>
>>> Signed-off-by: Magnus Fromreide <magfr(a)lysator.liu.se>
>>>
>>>
>> I will forward this on to Steve Rostedt. pevent code is not actually
>> strictly part of the powertop src, it is just temporarily being built as
>> part of the project so powertop can take advantage of it early.
> Thanks. I found no contact information for pevent but it feels like an
> imported library.
>
>> That said, it may not be a good fit for the grand scheme.
>> Which reminds me I need to push a readme explaining this.
> I am looking forward to it.
>
> Patch 2/2 depends on this, should I prepare an alternate version that
> doesn't trigger the bug in the pevent headers?
Maybe, but wait a day, you inspired me to completely update and rebase
the pevent code.
>
> /MF
>
next reply other threads:[~2012-07-26 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 22:09 Chris Ferron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-30 16:08 [Powertop] [PATCH 1/2] Make it possible to include parse-events.h before libc headers Chris Ferron
2012-07-28 17:27 Magnus Fromreide
2012-07-25 19:26 Magnus Fromreide
2012-07-25 17:44 Chris Ferron
2012-07-24 6:03 Magnus Fromreide
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=5011C02D.80805@linux.intel.com \
--to=powertop@lists.01.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.