> >There's e.g. no reason to ask all users whether they want to compile all >I/O schedulers into their kernel. > The users that do not know how to handle it should not be compiling a kernel. If in doubt, they should read the help texts and follow the "If unsure" clause listed there. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Adrian Bunk <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- References:
- [PATCH] BLOCK: Make it possible to disable the block layer
- From: David Howells <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Adrian Bunk <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: David Woodhouse <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Adrian Bunk <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: David Woodhouse <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Adrian Bunk <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Alexey Dobriyan <[email protected]>
- Re: [PATCH] BLOCK: Make it possible to disable the block layer
- From: Adrian Bunk <[email protected]>
- [PATCH] BLOCK: Make it possible to disable the block layer
- Prev by Date: Re: [PATCH] BLOCK: Make it possible to disable the block layer
- Next by Date: Re: [RFC][PATCH 3/4] (Refcount + Waitqueue) implementation for cpu_hotplug "locking"
- Previous by thread: Re: [PATCH] BLOCK: Make it possible to disable the block layer
- Next by thread: Re: [PATCH] BLOCK: Make it possible to disable the block layer
- Index(es):
 |