public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Len Brown <len.brown@intel.com>,
	Bob Moore <robert.moore@intel.com>,
	Lin Ming <ming.m.lin@intel.com>
Subject: Re: linux-next: Tree for March 27 (longhaul build error)
Date: Fri, 27 Mar 2009 16:44:33 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0903271644040.26419@localhost.localdomain> (raw)
In-Reply-To: <200903271842.37665.bzolnier@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 747 bytes --]


On Fri, 27 Mar 2009, Bartlomiej Zolnierkiewicz wrote:

> 
> Hi,
> 
> On Friday 27 March 2009, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20090326:
> 
> I hit the following build error using OpenSUSE's kernel config:
> 
> arch/x86/kernel/cpu/cpufreq/longhaul.c: In function ‘longhaul_setstate’:
> arch/x86/kernel/cpu/cpufreq/longhaul.c:308: error: implicit declaration of function ‘acpi_set_register’
> make[1]: *** [arch/x86/kernel/cpu/cpufreq/longhaul.o] Error 1
> make: *** [arch/x86/kernel/cpu/cpufreq/longhaul.o] Error 2
> 
> Len, it seems like the following patch managed to slip through the cracks:
> 
> 	http://patchwork.kernel.org/patch/12715/

Got it,
thanks Bart.

Len Brown, Intel Open Source Technology Center

      reply	other threads:[~2009-03-27 20:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 12:19 linux-next: Tree for March 27 Stephen Rothwell
2009-03-27 13:57 ` Next March 27 : s390 defconfig build failure Sachin Sant
2009-03-27 14:40   ` Heiko Carstens
2009-03-30  9:51     ` Sachin Sant
2009-03-27 16:48 ` linux-next: Tree for March 27 (netfilter build error) Randy Dunlap
2009-03-27 23:01   ` David Miller
2009-03-28 10:28     ` Cyrill Gorcunov
2009-03-29  4:26       ` Randy Dunlap
2009-03-29  6:47         ` Cyrill Gorcunov
2009-03-29  6:47           ` David Miller
2009-03-29 11:48             ` Harald Welte
2009-03-29 11:59             ` Pablo Neira Ayuso
2009-03-29 12:27               ` Cyrill Gorcunov
2009-03-29 20:46               ` David Miller
2009-03-30 12:00                 ` Patrick McHardy
2009-03-27 17:42 ` linux-next: Tree for March 27 (longhaul " Bartlomiej Zolnierkiewicz
2009-03-27 20:44   ` Len Brown [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=alpine.LFD.2.00.0903271644040.26419@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=robert.moore@intel.com \
    --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