From: Takashi Iwai <tiwai@suse•de>
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>
Subject: Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13)
Date: Thu, 13 Nov 2008 10:03:08 +0100 [thread overview]
Message-ID: <s5hiqqsq9pv.wl%tiwai@suse.de> (raw)
In-Reply-To: <20081113183316.3601c13d.sfr@canb.auug.org.au>
At Thu, 13 Nov 2008 18:33:16 +1100,
Stephen Rothwell wrote:
>
> Hi all,
>
> Changes since 20081112:
>
> Undropped tree:
> security-testing
>
> Dropped trees (temporarily):
> sh (build problems)
> creds (non-trivial conflict)
> userns (it depends on creds)
> semaphore-removal (due to unfixed conflicts against Linus' tree)
> firmware (unfixed build failure)
>
> The usb tree lost its conflict.
>
> The net tree lost its 3 conflicts.
The IDE tree update seems broken for some old devices.
CONFIG_IDE_LEGACY is selected by them but it's nowhere defined in
Kconfig.
Takashi
---
diff --git a/drivers/ide/Kconfig b/drivers/ide/Kconfig
index 6d85820..8d84fe4 100644
--- a/drivers/ide/Kconfig
+++ b/drivers/ide/Kconfig
@@ -62,6 +62,9 @@ config IDE_TIMINGS
config IDE_ATAPI
bool
+config IDE_LEGACY
+ bool
+
config BLK_DEV_IDE_SATA
bool "Support for SATA (deprecated; conflicts with libata SATA driver)"
default n
next prev parent reply other threads:[~2008-11-13 9:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 7:33 linux-next: Tree for November 13 Stephen Rothwell
2008-11-13 9:03 ` Takashi Iwai [this message]
2008-11-13 21:08 ` Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13) Bartlomiej Zolnierkiewicz
2008-11-13 17:36 ` linux-next: Tree for November 13 (v4l2 build error) Randy Dunlap
2008-11-13 17:55 ` linux-next: Tree for November 13 (auditsc) Randy Dunlap
2008-11-14 0:31 ` next-20081113: ndefined ureference to `freeze_processes' Alexey Dobriyan
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=s5hiqqsq9pv.wl%tiwai@suse.de \
--to=tiwai@suse$(echo .)de \
--cc=bzolnier@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/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