From: Dave Jones <davej@redhat.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] X86_GX_SUSPMOD must depend on PCI
Date: Thu, 19 Jan 2006 19:45:38 -0500 [thread overview]
Message-ID: <20060120004538.GD3798@redhat.com> (raw)
In-Reply-To: <20060120002537.GI19398@stusta.de>
On Fri, Jan 20, 2006 at 01:25:37AM +0100, Adrian Bunk wrote:
> This patch fixes the following compile error:
>
> ...
> CC arch/i386/kernel/cpu/cpufreq/gx-suspmod.o
> arch/i386/kernel/cpu/cpufreq/gx-suspmod.c: In function 'gx_detect_chipset':
> arch/i386/kernel/cpu/cpufreq/gx-suspmod.c:193: error: implicit declaration of function 'pci_match_id'
> arch/i386/kernel/cpu/cpufreq/gx-suspmod.c:193: warning: comparison between pointer and integer
> make[3]: *** [arch/i386/kernel/cpu/cpufreq/gx-suspmod.o] Error 1
>
> <-- snip -->
>
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Applied, thanks Adrian.
Dave
next prev parent reply other threads:[~2006-01-20 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 0:25 [2.6 patch] X86_GX_SUSPMOD must depend on PCI Adrian Bunk
2006-01-20 0:45 ` Dave Jones [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-08 20:20 Adrian Bunk
2005-11-21 22:33 Adrian Bunk
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=20060120004538.GD3798@redhat.com \
--to=davej@redhat.com \
--cc=bunk@stusta.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=linux-kernel@vger.kernel.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.