From: Matthew Wilcox <matthew@wil.cx>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Gwendal Grignou <gwendal@google.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH #upstream-fixes] libata: Add transport class for libata
Date: Tue, 19 Aug 2008 06:27:38 -0600 [thread overview]
Message-ID: <20080819122738.GC21854@parisc-linux.org> (raw)
In-Reply-To: <48AAAFAC.9050502@s5r6.in-berlin.de>
On Tue, Aug 19, 2008 at 01:34:04PM +0200, Stefan Richter wrote:
> Gwendal Grignou wrote:
> > This patch adds objects for accessing libata objects from user space:
> > - ata_port class: one per ATA port
> > - ata_link class: one per ATA port or 15 for SATA Port Multiplier
> > - ata_device class: up to 2 for PATA link, usually one for SATA.
>
> Two outsider questions:
>
> You are adding a userspace interface. What are the stability commitments?
To channel GregKH, you need to document them in Documentation/ABI/
> Could you make it configurable, so that people who don't need this
> interface can build the kernel without it?
Please, no. Don't we already have enough CONFIG options?
I think a more important question is ... this is coming from a Google
address, but has a Copyright Dell on it. Where's the sign-off chain for
this? Who's the author really?
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-08-19 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 4:31 [PATCH #upstream-fixes] libata: Add transport class for libata Gwendal Grignou
2008-08-19 11:34 ` Stefan Richter
2008-08-19 12:27 ` Matthew Wilcox [this message]
2008-08-19 13:04 ` Stefan Richter
2008-08-19 13:16 ` Stefan Richter
2008-08-19 13:41 ` Stefan Richter
2008-08-19 18:14 ` Gwendal Grignou
2008-08-20 8:17 ` Tejun Heo
2008-08-20 18:55 ` Gwendal Grignou
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=20080819122738.GC21854@parisc-linux.org \
--to=matthew@wil.cx \
--cc=gwendal@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).