All of lore.kernel.org
 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: Thu, 17 Apr 2008 10:59:16 +0100	[thread overview]
Message-ID: <20080417095916.GD1449@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080417093753.GF1677@cs181133002.pp.htv.fi>

On Thu, Apr 17, 2008 at 12:37:53PM +0300, Adrian Bunk wrote:
> Any objections against the patch below?

Let's look at the rest of the situation surrounding HAVE_IDE first.
It's something of a mess:

avr32, m68knommu, ppc, s390 and v850 do not have asm/ide.h

avr32, m68knommu, ppc, v850 all set HAVE_IDE, arch/s390/Kconfig contains
no reference.

avr32 supports PATA (which is IDE).

Everything else provides an asm/ide.h and sets HAVE_IDE.

So:

Q1. Do avr32, m68knommu, ppc, v850 have IDE support or do they not?
Q2. Should avr32, m68knommu, ppc, v850 supply an asm/ide.h header?
Q3. Is it worth supporting HAVE_IDE for all kernel architectures when
    its just one (s390) which supports neither IDE nor ATA - or would
    something more generic covering both be appropriate.

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

  reply	other threads:[~2008-04-17  9:59 UTC|newest]

Thread overview: 26+ 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 14:16 ` 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: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-15 23:26                     ` Bartlomiej Zolnierkiewicz
2008-04-17  9:37                     ` [2.6 patch] ARM: always " Adrian Bunk
2008-04-17  9:59                       ` Russell King [this message]
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
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=20080417095916.GD1449@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 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.