Re: RFC: ACPI/scsi/libata integration and hotswap

[Erik Slagter <erik@slagter.name>]

On Fri, 2005-12-09 at 11:39 +0100, Jens Axboe wrote:

> > IMHO available infrastructure (and hardware abstraction!) should be used
> > instead of being stubborn and pretend we know everything about any
> > hardware.
> 
> It's not about being stubborn, it's about maintaining and working on a
> clean design. The developers have to do that, not the users. So forgive
> people for being a little cautious about shuffling all sorts of ACPI
> into the scsi core and/or drivers. We always need to think long term
> here.
> 
> Users don't care about the maintainability and cleanliness of the code,
> they really just want it to work. Which is perfectly understandable.

I perfectly understand that, what I do object against, is rejecting a
concept (like this) totally because the developers(?) do not like the
mechanism that's used (although ACPI is used everywhere else in the
kernel). At least there might be some discussion where this sort of code
belongs to make the design clean and easily maintainable, instead of
instantly completely rejecting the concept, because OP simply doesn't
like acpi.

Attachment: smime.p7s
Description: S/MIME cryptographic signature