linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Adrian Bunk <bunk@kernel.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-pcmcia@lists.infradead.org
Subject: Re: [2.6 patch] ARM: always select HAVE_IDE
Date: Sat, 19 Apr 2008 12:33:56 +0100	[thread overview]
Message-ID: <20080419113356.GA6974@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080417132507.GA9314@cs181133002.pp.htv.fi>

On Thu, Apr 17, 2008 at 04:25:07PM +0300, Adrian Bunk wrote:
> You have a point that one might argue that avr32 should also select 
> HAVE_IDE and get an asm/ide.h .
> 
> The main difference between avr32 and arm is that on arm there are a 
> bunch of platforms that actually want to use drivers/ide/ at the moment, 
> and the fine-grained select's we have at the moment don't bring any real 
> gain.
> 
> I do actually not care much how this gets resolved (we could even 
> ditch HAVE_IDE and provide asm/ide.h on all architectures) if there's 
> general agreement that this is the way to go.

That is probably a more correct approach.

Consider that if you do have PCMCIA, then you can plug a CF card in and,
therefore, you have an IDE interface in the system.  So, selecting
HAVE_IDE if PCMCIA is enabled is entirely reasonable.  What isn't so
reasonable is not providing asm/ide.h if your architecture has the
possibility of supporting PCMCIA.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2008-04-19 11:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 14:16 [2.6 patch] PCMCIA mustn't select HAVE_IDE Adrian Bunk
2008-04-14 17:53 ` Sam Ravnborg
2008-04-15 20:15   ` Bartlomiej Zolnierkiewicz
2008-04-15 21:23     ` Adrian Bunk
2008-04-15 21:28       ` Russell King
2008-04-15 21:42         ` Russell King
2008-04-15 21:52           ` Adrian Bunk
2008-04-15 22:03             ` Russell King
2008-04-15 22:10               ` Adrian Bunk
2008-04-15 22:39                 ` Russell King
2008-04-15 23:26                   ` Bartlomiej Zolnierkiewicz
2008-04-17  9:37                     ` [2.6 patch] ARM: always " Adrian Bunk
2008-04-17  9:59                       ` Russell King
2008-04-17 10:48                         ` Adrian Bunk
2008-04-17 11:00                           ` Russell King
2008-04-17 13:25                             ` Adrian Bunk
2008-04-19 11:33                               ` Russell King [this message]
2008-04-27 18:32                               ` Bartlomiej Zolnierkiewicz
2008-04-27 20:29                                 ` Sam Ravnborg
2008-04-27 21:06                                   ` Bartlomiej Zolnierkiewicz
2008-04-17 12:38                           ` Matthew Wilcox
2008-04-27 17:53                       ` Bartlomiej Zolnierkiewicz
2008-04-15 21:26     ` [2.6 patch] PCMCIA mustn't " Russell 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=20080419113356.GA6974@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=bunk@kernel.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.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).