From: Thomas Renninger <trenn@suse.de>
To: "Shreyas B. Prabhu" <shreyas@linux.vnet.ibm.com>
Cc: rafael.j.wysocki@intel.com, jtanenba@redhat.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpupower: Fix build error in cpufreq-info
Date: Wed, 17 Feb 2016 15:29:45 +0100 [thread overview]
Message-ID: <5255546.ocxDsFsmcy@skinner> (raw)
In-Reply-To: <1453130083-16055-1-git-send-email-shreyas@linux.vnet.ibm.com>
On Monday, January 18, 2016 08:44:43 PM Shreyas B. Prabhu wrote:
> Fix the following build error by including limits.h -
>
> utils/cpufreq-info.c: In function ‘get_latency’:
> utils/cpufreq-info.c:437:29: error: ‘UINT_MAX’ undeclared (first use in
> this function)
> if (!latency || latency == UINT_MAX) {
> ^
> Signed-off-by: Shreyas B. Prabhu <shreyas@linux.vnet.ibm.com>
Signed-off-by: Thomas Renninger <trenn@suse.com>
Builds for me by luck, thanks!
Thomas
prev parent reply other threads:[~2016-02-17 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 15:14 [PATCH] cpupower: Fix build error in cpufreq-info Shreyas B. Prabhu
2016-02-17 14:29 ` Thomas Renninger [this message]
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=5255546.ocxDsFsmcy@skinner \
--to=trenn@suse.de \
--cc=jtanenba@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=shreyas@linux.vnet.ibm.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).