Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Adrian Bunk <bunk@xxxxxxxxx>
Subject: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
From: Roman Zippel <zippel@xxxxxxxxxxxxxx>
Date: Thu, 31 Aug 2006 00:41:02 +0200 (CEST)
Cc: Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Christoph Hellwig <hch@xxxxxxxxxxxxx>, David Howells <dhowells@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20060830214356.GO18276@xxxxxxxxx>
References: <20060825142753.GK10659@xxxxxxxxxxxxx> <20060824213252.21323.18226.stgit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20060824213334.21323.76323.stgit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <10117.1156522985@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <15945.1156854198@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20060829122501.GA7814@xxxxxxxxxxxxx> <44F44639.90103@xxxxxxxxxxxxxxxxx> <44F44B8D.4010700@xxxxxxxxxxxxxxxxx> <Pine.LNX.4.64.0608300311430.6761@xxxxxxxxxx> <44F5DA00.8050909@xxxxxxxxxxxxxxxxx> <20060830214356.GO18276@xxxxxxxxx>

Hi,

On Wed, 30 Aug 2006, Adrian Bunk wrote:

> USB_STORAGE switched from a depending on SCSI to select'ing SCSI three 
> years ago, and ATA in 2.6.19 will also select SCSI for a good reason:

It was already silly three years ago.

> When doing anything kconfig related, you must always remember that the 
> vast majority of kconfig users are not kernel hackers.

What does that mean, that only kernel hackers can read?

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: David Woodhouse
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Adrian Bunk

References:
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Christoph Hellwig
- [PATCH 01/17] BLOCK: Move functions out of buffer code [try #2]
  - From: David Howells
- [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: David Howells
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: David Howells
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: David Howells
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Christoph Hellwig
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Stefan Richter
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Stefan Richter
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Roman Zippel
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Stefan Richter
- Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
  - From: Adrian Bunk

Prev by Date: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
Next by Date: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
Previous by thread: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
Next by thread: Re: [PATCH 17/17] BLOCK: Make it possible to disable the block layer [try #2]
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]