From: Prarit Bhargava <prarit@redhat.com>
To: Shuah Khan <shuahkh@osg.samsung.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Stafford Horne <shorne@gmail.com>, Shuah Khan <shuah@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Thomas Renninger <trenn@suse.com>
Subject: Re: [PATCH v2] cpupower: Fix no-rounding MHz frequency output
Date: Thu, 2 Nov 2017 16:18:32 -0400 [thread overview]
Message-ID: <012f54bd-b4cc-22fb-83d4-9606ba7c50c8@redhat.com> (raw)
In-Reply-To: <126a1373-cd76-3f1e-2f91-5b5ea8a664ec@osg.samsung.com>
On 11/02/2017 02:59 PM, Shuah Khan wrote:
> On 11/01/2017 06:42 PM, Prarit Bhargava wrote:
>
> Hi Prarit,
>
> Does this tool build for you? I am seeing:
>
> utils/helpers/amd.c:7:21: fatal error: pci/pci.h: No such file or directory
> #include <pci/pci.h>
> ^
> compilation terminated.
> Makefile:221: recipe for target 'utils/helpers/amd.o' failed
> make: *** [utils/helpers/amd.o] Error 1
>
Got it ... you have to have the pciutils-devel package installed which
installs /usr/include/pci/pci.h.
That file contains:
struct pci_access {
/* Options you can change: */
unsigned int method; /* Access method */
int writeable; /* Open in read/write mode */
int buscentric; /* Bus-centric view of the world */
<snip>
P.
> thanks,
> -- Shuah
>
next prev parent reply other threads:[~2017-11-02 20:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 13:51 [PATCH v2] cpupower: Fix no-rounding MHz frequency output Prarit Bhargava
2017-10-25 22:01 ` Stafford Horne
2017-11-01 21:01 ` Shuah Khan
2017-11-01 21:00 ` Shuah Khan
2017-11-01 21:33 ` Rafael J. Wysocki
2017-11-01 21:38 ` Shuah Khan
2017-11-01 21:46 ` Rafael J. Wysocki
2017-11-01 21:49 ` Shuah Khan
2017-11-01 22:07 ` Rafael J. Wysocki
2017-11-01 22:30 ` Shuah Khan
2017-11-01 22:34 ` Rafael J. Wysocki
2017-11-02 0:42 ` Prarit Bhargava
2017-11-02 18:59 ` Shuah Khan
2017-11-02 19:43 ` Prarit Bhargava
2017-11-02 20:05 ` Prarit Bhargava
2017-11-02 20:18 ` Prarit Bhargava [this message]
2017-11-02 20:20 ` Shuah Khan
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=012f54bd-b4cc-22fb-83d4-9606ba7c50c8@redhat.com \
--to=prarit@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=shorne@gmail.com \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=trenn@suse.com \
/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;
as well as URLs for NNTP newsgroup(s).