From: Chris Ferron <chris.e.ferron at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] Get rid of ncurses' TRUE and FALSE
Date: Mon, 23 Jul 2012 08:09:16 -0700 [thread overview]
Message-ID: <500D691C.9090603@linux.intel.com> (raw)
In-Reply-To: 500D506D.8060204@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
On 07/23/2012 06:23 AM, Arjan van de Ven wrote:
> On 7/23/2012 12:31 AM, Magnus Fromreide wrote:
>
>>> Without it PowerTOP will not know what system call number
>>> __NR_perf_event_open has on ARM.
>> Why can't it take __NR_perf_event_open from the libc headers?
>> That is, why can't the whole ifdef under /* some people have stale
>> headers */ go?
>>
>> Powertop is rather demanding with regards to the environment anyhow and
>> magic constants are never fun.
> 100% agreed; I briefly talked to Chris on Friday based on this patch and
> that is the conclusion we came to as well.
This fix went in Friday as well. We should be now taking
__NR_perf_event_open from sys/syscall.h now.
>
>
> _______________________________________________
> PowerTop mailing list
> PowerTop(a)lists.01.org
> https://lists.01.org/mailman/listinfo/powertop
next reply other threads:[~2012-07-23 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:09 Chris Ferron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-23 13:23 [Powertop] [PATCH] Get rid of ncurses' TRUE and FALSE Arjan van de Ven
2012-07-23 7:48 Igor Zhbanov
2012-07-23 7:31 Magnus Fromreide
2012-07-23 6:32 Igor Zhbanov
2012-07-20 17:32 Chris Ferron
2012-07-20 7:06 Igor Zhbanov
2012-07-19 20:26 Arjan van de Ven
2012-07-19 20:20 Chris Ferron
2012-07-18 22:02 Chris Ferron
2012-07-18 13:21 Igor Zhbanov
2012-07-18 13:11 Arjan van de Ven
2012-07-18 9:17 Igor Zhbanov
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=500D691C.9090603@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.