LKML Archive on
help / color / mirror / Atom feed
From: Alan Stern <>
To: Greg KH <>
Cc: Kernel development list <>,
	Sarah Bailey <>,
	USB development list <>
Subject: Re: [linux-usb-devel] usbfs2: Why asynchronous I/O?
Date: Sun, 25 Feb 2007 21:22:54 -0500 (EST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, 25 Feb 2007, Greg KH wrote:

> On Sun, Feb 25, 2007 at 11:51:46AM -0500, Alan Stern wrote:
> > This deserves to be discussed on LKML.
> Are you sure?  I thought it already got pretty well answered on the USB
> mailing list (see David's response for one such response.)

Well, I was sure at the time I forwarded the message, which was hours 
before David's response arrived.

Besides, Sarah's message did bring up issues of interest to the kernel 
community at large, such as why AIO is supported by so few drivers.

Alan Stern

  reply	other threads:[~2007-02-26  2:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070225085755.GA4886@localdomain>
     [not found] ` <>
     [not found]   ` <>
2007-02-25 16:51     ` Alan Stern
2007-02-25 23:55       ` Greg KH
2007-02-26  2:22         ` Alan Stern [this message]
2007-02-26  8:54       ` Sarah Bailey
2007-02-27  0:20         ` Greg KH
2007-02-28 20:03         ` David Brownell
2007-02-25 17:42 David Brownell

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [linux-usb-devel] usbfs2: Why asynchronous I/O?' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).