From: Lee Revell <rlrevell@joe-job.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11, USB: High latency?
Date: Wed, 30 Mar 2005 20:21:26 -0500 [thread overview]
Message-ID: <1112232086.19975.30.camel@mindpipe> (raw)
In-Reply-To: <200503301713.19920.david-b@pacbell.net>
On Wed, 2005-03-30 at 17:13 -0800, David Brownell wrote:
> On Wednesday 30 March 2005 4:43 pm, Lee Revell wrote:
> > On Wed, 2005-03-30 at 14:57 -0800, David Brownell wrote:
> > > Quoth rlevell@joe-job.com:
> > > > I think this is connected to a problem people have been reporting on the
> > > > Linux audio lists. With some USB chipsets, USB audio interfaces just
> > > > don't work. There are dropouts even at very high latencies.
> >
> > Please don't trim cc: lists. Always use reply-to-all for LKML mail.
>
> Please don't assume everyone subscribes to LKML, or that
> everything crafted to be threaded more-or-less-correctly
> was really crafted with any kind of "reply" command. :)
Um, that's exactly why reply-to-all should be used, because not everyone
who posts to LKML subscribes to the list. Otherwise, you'd either have
to make everyone who posts a question or a bug report subscribe to the
list to see the replies, or place the burden on the responder to keep
track of who wants to be cc'ed and who doesn't.
Beaised, even if you disagree with them, when you post to LKML you abide
by the LKML rules. It's up to you to know what those are.
Lee
next prev parent reply other threads:[~2005-03-31 1:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 22:57 2.6.11, USB: High latency? David Brownell
2005-03-31 0:43 ` Lee Revell
2005-03-31 1:13 ` David Brownell
2005-03-31 1:21 ` Lee Revell [this message]
2005-03-31 1:32 ` David Brownell
2005-03-31 0:51 ` Lee Revell
2005-03-31 1:28 ` David Brownell
2005-03-31 1:32 ` Lee Revell
2005-03-31 1:40 ` David Brownell
2005-03-31 1:44 ` Lee Revell
2005-03-31 1:39 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 8:03 kus Kusche Klaus
2005-04-04 8:36 ` Ingo Molnar
2005-04-04 19:40 ` Alan Stern
2005-04-01 13:16 kus Kusche Klaus
2005-04-01 13:41 ` Ingo Molnar
2005-04-01 6:46 kus Kusche Klaus
2005-04-01 17:20 ` Alan Stern
2005-03-31 12:12 kus Kusche Klaus
2005-03-31 11:15 kus Kusche Klaus
2005-03-31 16:48 ` Alan Stern
2005-03-30 13:51 kus Kusche Klaus
2005-03-30 15:55 ` Alan Stern
2005-03-30 21:28 ` Lee Revell
2005-03-31 11:30 ` Ingo Molnar
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=1112232086.19975.30.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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