From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Len Brown <lenb@kernel•org>
Cc: linux-next@vger•kernel.org,
Venki Pallipadi <venkatesh.pallipadi@intel•com>,
Andy Henroid <andrew.d.henroid@intel•com>
Subject: linux-next: acpi tree build failure
Date: Wed, 15 Oct 2008 15:51:48 +1100 [thread overview]
Message-ID: <20081015155148.d0cf5553.sfr@canb.auug.org.au> (raw)
Hi Len,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
scripts/Makefile.build:41: drivers/idle/Makefile: No such file or directory
make[3]: *** No rule to make target `drivers/idle/Makefile'.
Caused by commit e8b529091b2ab65f5a4783e292c2b472e309116e ("i7300_idle
driver v1.55"). I added the patch below.
I suspect that some patch was missed ...
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Wed, 15 Oct 2008 15:32:35 +1100
Subject: [PATCH] drivers has no idle subdirectory
Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
arch/x86/Kconfig | 2 --
drivers/Makefile | 1 -
2 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 5eb231a..8dbd14c 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1686,8 +1686,6 @@ source "arch/x86/kernel/cpu/cpufreq/Kconfig"
source "drivers/cpuidle/Kconfig"
-source "drivers/idle/Kconfig"
-
endmenu
diff --git a/drivers/Makefile b/drivers/Makefile
index f443a8a..2735bde 100644
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -82,7 +82,6 @@ obj-$(CONFIG_EISA) += eisa/
obj-y += lguest/
obj-$(CONFIG_CPU_FREQ) += cpufreq/
obj-$(CONFIG_CPU_IDLE) += cpuidle/
-obj-y += idle/
obj-$(CONFIG_MMC) += mmc/
obj-$(CONFIG_MEMSTICK) += memstick/
obj-$(CONFIG_NEW_LEDS) += leds/
--
1.5.6.5
next reply other threads:[~2008-10-15 5:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 4:51 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-14 1:20 linux-next: acpi tree build failure Stephen Rothwell
2009-12-14 19:20 ` Bjorn Helgaas
2009-12-15 4:57 ` Bjorn Helgaas
2009-12-15 22:37 ` Len Brown
2009-12-15 23:28 ` Stephen Rothwell
2009-12-16 2:28 ` Stephen Rothwell
2009-09-26 2:15 Stephen Rothwell
2009-09-26 3:11 ` Bjorn Helgaas
2009-09-27 1:27 ` Crane Cai
2009-09-27 7:54 ` Len Brown
2009-09-01 2:57 Stephen Rothwell
2009-09-07 13:46 ` Stephen Rothwell
2009-09-08 0:47 ` Zhang Rui
2009-09-09 4:02 ` Len Brown
2009-09-09 5:45 ` Stephen Rothwell
2009-06-30 3:16 Stephen Rothwell
2009-07-06 6:18 ` Stephen Rothwell
2009-07-07 3:17 ` Len Brown
2009-07-07 3:53 ` Stephen Rothwell
2009-04-24 4:46 Stephen Rothwell
2009-04-24 15:15 ` Len Brown
2009-03-18 0:57 Stephen Rothwell
2009-03-18 1:09 ` Lin Ming
2009-03-18 3:27 ` Stephen Rothwell
2009-03-27 20:49 ` Len Brown
2009-02-24 4:37 Stephen Rothwell
2009-03-03 1:47 ` Stephen Rothwell
2009-03-16 5:10 ` Stephen Rothwell
2009-03-27 20:58 ` Len Brown
2009-02-02 2:22 Stephen Rothwell
2009-02-05 2:13 ` Stephen Rothwell
2009-02-05 5:00 ` Greg KH
2009-02-07 4:06 ` Len Brown
2009-02-07 5:32 ` Greg KH
2008-10-15 5:08 Stephen Rothwell
2008-10-15 5:15 ` Shaohua Li
2008-08-12 3:16 Stephen Rothwell
2008-08-12 7:06 ` Andi Kleen
2008-08-12 20:07 ` Carlos Corbacho
2008-08-12 21:29 ` Carlos Corbacho
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=20081015155148.d0cf5553.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andrew.d.henroid@intel$(echo .)com \
--cc=lenb@kernel$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=venkatesh.pallipadi@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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