linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux arch <linux-arch@vger.kernel.org>,
	linux-ide@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC] Introduce HAVE_IDE to support flexible IDE per arch configuration
Date: Thu, 7 Feb 2008 21:54:21 +0000	[thread overview]
Message-ID: <20080207215421.GJ28435@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080207214256.GA22572@uranus.ravnborg.org>

On Thu, Feb 07, 2008 at 10:42:56PM +0100, Sam Ravnborg wrote:
> Following patch introduce HAVE_IDE to support flexible per
> arch or even per. sub-arch configuration of IDE support.
> This patch is needed to allow arm to use the generic
> drivers/Kconfig file.
> 
> Introducing HAVE_IDE so each arch explicit select HAVE_IDE
> if supported allowed us to get rid of HAS_IOMEM which
> is anyway overloaded.
> And doing it this way is a much better way to document which
> architectures that supports IDE.
> Furthermore the decision if IDE is supported or not is
> distributed.
> Consider seeing this all over:
> 
> -if PCMCIA || ARCH_CLPS7500 || ARCH_IOP32X || ARCH_IOP33X || ARCH_IXP4XX \
> -       || ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
> -       || ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE \
> -       || ARCH_IXP23XX
>  source "drivers/ide/Kconfig"
> -endif
> 
> Only s390 and um does not support IDE from my quick
> investigation, if there are others let me know.
> [Added linux-arch to catch all arch maintainers].
> 
> Comments?

Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>

  reply	other threads:[~2008-02-07 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 21:42 [RFC] Introduce HAVE_IDE to support flexible IDE per arch configuration Sam Ravnborg
2008-02-07 21:54 ` Russell King - ARM Linux [this message]
2008-02-08 20:04 ` Sam Ravnborg
2008-02-08 20:26   ` Bartlomiej Zolnierkiewicz

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=20080207215421.GJ28435@flint.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).