From: Andi Kleen <andi@firstfloor.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Andi Kleen <andi@firstfloor.org>, Matthew Wilcox <matthew@wil.cx>,
Jon Watte <jwatte@gmail.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: AHCI finds disks; no /dev/sd inodes bound?
Date: Thu, 10 Jan 2008 01:38:06 +0100 [thread overview]
Message-ID: <20080110003806.GD18480@one.firstfloor.org> (raw)
In-Reply-To: <478552DF.1050203@s5r6.in-berlin.de>
On Thu, Jan 10, 2008 at 12:03:59AM +0100, Stefan Richter wrote:
> Andi Kleen wrote:
> > On Wed, Jan 09, 2008 at 10:41:59PM +0100, Stefan Richter wrote:
> >> However, this further obfuscates the fact that libata uses Linux' SCSI
> >> midlayer and highlevel. Which is a bad thing. For example, there are
> >
> > People are not interested in how libata is implemented internally.
> > They just want their SATA interfaces to work.
> >
> > Kconfig is also not an educational facility or high level
> > design description of the code, but a pragmatic tool to get the job
> > done.
>
> I did not talk about education or design decription. I did talk about
> appropriately showing what the Kconfig options do.
That's "high level design description"
-Andi
next prev parent reply other threads:[~2008-01-10 0:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 7:40 AHCI finds disks; no /dev/sd inodes bound? Jon Watte
2008-01-09 16:45 ` Andi Kleen
2008-01-09 17:21 ` Jon Watte
2008-01-09 17:29 ` James Bottomley
2008-01-09 17:49 ` Andi Kleen
2008-01-09 18:33 ` Stefan Richter
2008-01-09 18:37 ` Stefan Richter
2008-01-09 18:50 ` Stefan Richter
2008-01-09 20:36 ` Jon Watte
2008-01-09 20:58 ` Matthew Wilcox
2008-01-09 21:41 ` Stefan Richter
2008-01-09 22:23 ` Andi Kleen
2008-01-09 23:03 ` Stefan Richter
2008-01-09 23:16 ` Stefan Richter
2008-01-10 0:38 ` Andi Kleen [this message]
2008-01-10 0:53 ` Stefan Richter
2008-01-10 4:47 ` Jeff Garzik
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=20080110003806.GD18480@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jwatte@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=stefanr@s5r6.in-berlin.de \
/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.