From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: David Brownell <david-b@pacbell.net>,
Maxim Levitsky <maximlevitsky@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Greg KH <greg@kroah.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kernel development list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: Re: [linux-pm] [PATCH v2] Add suspend/resume for HPET
Date: Mon, 2 Apr 2007 10:09:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704021007440.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0704021000450.1743-100000@netrider.rowland.org>
On Mon, 2 Apr 2007, Alan Stern wrote:
>
> Would you mind retracting this patch? It will interfere with some work
> I've been doing in USB, work that relies on exactly the sort of multiple
> power dependency you mention.
I agree. We should just make the damn timers be added at the right point.
We can for example *add* the devices early, even if we then actually start
using them at some later date.
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
Thomas Gleixner <tglx@linutronix.de>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Add suspend/resume for HPET
Date: Mon, 2 Apr 2007 10:09:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704021007440.6730@woody.linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0704021000450.1743-100000@netrider.rowland.org>
On Mon, 2 Apr 2007, Alan Stern wrote:
>
> Would you mind retracting this patch? It will interfere with some work
> I've been doing in USB, work that relies on exactly the sort of multiple
> power dependency you mention.
I agree. We should just make the damn timers be added at the right point.
We can for example *add* the devices early, even if we then actually start
using them at some later date.
Linus
next prev parent reply other threads:[~2007-04-02 17:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 14:16 [linux-pm] [PATCH v2] Add suspend/resume for HPET Alan Stern
2007-04-02 17:09 ` Linus Torvalds [this message]
2007-04-02 17:09 ` Linus Torvalds
2007-04-02 19:16 ` [linux-pm] " David Brownell
2007-04-02 19:16 ` David Brownell
2007-04-02 20:04 ` [linux-pm] " Alan Stern
2007-04-02 20:04 ` Alan Stern
2007-04-03 5:54 ` [linux-pm] " Thomas Gleixner
2007-04-03 5:54 ` Thomas Gleixner
2007-04-04 15:06 ` [linux-pm] " David Brownell
2007-04-04 15:06 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2007-03-16 16:33 Linux 2.6.21-rc4 Linus Torvalds
2007-03-31 16:33 ` [PATCH v2] Add suspend/resume for HPET Thomas Gleixner
2007-03-31 16:53 ` Linus Torvalds
2007-03-31 17:02 ` Ingo Molnar
2007-03-31 18:18 ` [linux-pm] " David Brownell
2007-03-31 19:32 ` David Brownell
2007-04-01 3:13 ` Jeff Chua
2007-04-01 4:13 ` David Brownell
2007-03-31 17:55 ` David Brownell
2007-03-31 17:55 ` 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:
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=Pine.LNX.4.64.0704021007440.6730@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=maximlevitsky@gmail.com \
--cc=mingo@elte.hu \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.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.