All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian King <brking@us.ibm.com>
To: Paul Mackerras <paulus@samba.org>
Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org, torvalds@osdl.org,
	James Bottomley <jejb@mulgrave.il.steeleye.com>
Subject: Re: ipr SATA support is causing problems
Date: Fri, 10 Nov 2006 09:23:14 -0600	[thread overview]
Message-ID: <45549962.108@us.ibm.com> (raw)
In-Reply-To: <17748.25705.543922.486456@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Brian,
> 
> Today I compiled up a kernel from Linus' git tree and tried it on a
> POWER6 partition.  First I found that my config no longer had the ipr
> driver, because I didn't have CONFIG_ATA and ipr now depends on
> CONFIG_ATA.  So I enabled CONFIG_ATA without enabling any of the ATA
> chip drivers, which seems a little weird, and re-enabled ipr.

I'm not sure what the best way to fix this one is... The ideal way is to
change ipr to select CONFIG_ATA, but kconfig currently doesn't handle
that and complains about recursive dependencies since IPR depends on
CONFIG_SCSI and CONFIG_ATA selects CONFIG_SCSI. I'm guessing the
libsas SATA usage has similar problems. Right now we both use a depends
CONFIG_ATA statement. Ideally, kconfig should be fixed to handle this.

Brian

-- 
Brian King
eServer Storage I/O
IBM Linux Technology Center

  parent reply	other threads:[~2006-11-10 15:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 11:37 ipr SATA support is causing problems Paul Mackerras
2006-11-10 11:48 ` Josh Boyer
2006-11-10 12:07   ` Paul Mackerras
2006-11-10 13:14     ` Josh Boyer
2006-11-10 15:07       ` Brian King
2006-11-10 15:23 ` Brian King [this message]
2006-11-10 23:06   ` Paul Mackerras
2006-11-11 23:56     ` Brian King
2006-11-12  0:50       ` Benjamin Herrenschmidt
2006-11-12  3:55         ` Brian King

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=45549962.108@us.ibm.com \
    --to=brking@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=jejb@mulgrave.il.steeleye.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=torvalds@osdl.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.