All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13)
Date: Thu, 13 Nov 2008 22:08:42 +0100	[thread overview]
Message-ID: <200811132208.43694.bzolnier@gmail.com> (raw)
In-Reply-To: <s5hiqqsq9pv.wl%tiwai@suse.de>

On Thursday 13 November 2008, Takashi Iwai wrote:
> 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.

Thanks for noticing and fixing this.

I've integrated your fix into the guilty patch ("ide: move legacy
ISA/VLB ports handling to ide-legacy.c") to preserve bisectability.

Bart

  reply	other threads:[~2008-11-13 21:13 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 ` Missing CONFIG_IDE_LEGACY definition (Re: linux-next: Tree for November 13) Takashi Iwai
2008-11-13 21:08   ` Bartlomiej Zolnierkiewicz [this message]
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=200811132208.43694.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    /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.