From: Dave Jones <davej@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Kurt Roeckx <kurt@roeckx.be>
Subject: Re: linux-next: cpufreq-current tree build warning
Date: Wed, 16 Sep 2009 22:27:26 -0400 [thread overview]
Message-ID: <20090917022726.GA30706@redhat.com> (raw)
In-Reply-To: <20090917120651.f0cdf4c2.sfr@canb.auug.org.au>
On Thu, Sep 17, 2009 at 12:06:51PM +1000, Stephen Rothwell wrote:
> Hi Dave,
>
> Today's linux-next build (x86_64 allmodconfig) produced this warning:
>
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c: In function 'fill_powernow_table_fidvid':
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c:1001: warning: passing argument 1 of 'invalidate_entry' from incompatible pointer type
> arch/x86/kernel/cpu/cpufreq/powernow-k8.c:608: note: expected 'struct cpufreq_frequency_table *' but argument is of type 'struct powernow_k8_data *'
>
> Introduced by commit 7fc1b26613587ab4369615445b5485040c60fef1 ("[CPUFREQ]
> Fix NULL ptr regression in powernow-k8").
Hi Stephen,
I'm very confused. I don't see this..
(22:22:25:davej:cpufreq)$ make arch/x86/kernel/cpu/cpufreq/powernow-k8.o
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-x86
CALL scripts/checksyscalls.sh
CC [M] arch/x86/kernel/cpu/cpufreq/powernow-k8.o
(22:22:30:davej:cpufreq)$
Also, line 1001 is ..
if (data->acpi_data.state_count)
So I'm not sure what your gcc is talking about.
Does next contain additional patches to this file from outside the cpufreq.git tree?
Dave
next prev parent reply other threads:[~2009-09-17 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 2:06 linux-next: cpufreq-current tree build warning Stephen Rothwell
2009-09-17 2:27 ` Dave Jones [this message]
2009-09-17 2:55 ` Stephen Rothwell
2009-09-17 3:17 ` Dave Jones
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=20090917022726.GA30706@redhat.com \
--to=davej@redhat.com \
--cc=kurt@roeckx.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).