mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Patrick Mochel <mochel@digitalimplant.org>, linux-kernel@vger.kernel.org
Cc: David Brownell <david-b@pacbell.net>,
	Alan Stern <stern@rowland.harvard.edu>,
	Pavel Machek <pavel@suse.cz>, "" <greg@kroah.com>
Subject: Re: Linux PM core problems
Date: Mon, 27 Sep 2004 19:34:32 +0200	[thread overview]
Message-ID: <200409271934.32759.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.50.0409270953140.32506-100000@monsoon.he.net>

Am Montag, 27. September 2004 19:02 schrieb Patrick Mochel:
> 
> On Mon, 27 Sep 2004, David Brownell wrote:
> 
> > What, the audience that understands USB shouldn't be expected
> > to (a) discuss USB-related PM issues, except on non-USB lists; or
> > (b) involve developers who know other parts of PM?  Nonsense.
> 
> I didn't say that. But, the thread (especially given the Subject) is about
> how the core works. And, most of the relevant USB people seem to be on
> linux-kernel, or can easily be cc'd as well. And, what about Benh, who has
> suffered through this problems on ppc for just as long?

OK, the cc list can easily be extended.

[..]
> > There's been a notable lack of discussion about USB-related PM issues,
> > except in these recent threads.  So "read the archives" isn't constructive.
> 
> This thread seems to lack USB-centricity. I know you've read the archives
> and have participated in the discussions. But most, if not all, of the
> ideas have come up in one form or another (though many with poor timing).
> We're re-hashing the same discussion over and over. Not that that is a bad
> thing, because eventually someone will get sick of reading it all just fix
> the stupid code.
> 
> My issue is that core problems are being talked about on a splinter list
> and they should move to linux-kernel. But, if we're going to do that, it's
> imperative to understand the history and the context, and know that we
> have the same problem as we did 4 years ago (albeit with a different
> playing field).

Why? What makes this field so hard?
Would you be happy if we listed the problems USB has with the current code?

	Regards
		Oliver

           reply	other threads:[~2004-09-27 17:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Pine.LNX.4.50.0409270953140.32506-100000@monsoon.he.net>]

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=200409271934.32759.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@suse.cz \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®