From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Zoran Markovic <zoran.markovic@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org,
Shaibal Dutta <shaibal.dutta@broadcom.com>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Xenia Ragiadakou <burzalodowa@gmail.com>,
Julius Werner <jwerner@chromium.org>,
Krzysztof Mazur <krzysiek@podlesie.net>,
Matthias Beyer <mail@beyermatthias.de>,
Dan Williams <dan.j.williams@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Thomas Pugliese <thomas.pugliese@gmail.com>
Subject: Re: [RFC PATCHv2] usb: move hub init and LED blink work to power efficient workqueue
Date: Fri, 7 Feb 2014 07:28:28 -0800 [thread overview]
Message-ID: <20140207152828.GA11557@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1402071018400.1326-100000@iolanthe.rowland.org>
On Fri, Feb 07, 2014 at 10:20:57AM -0500, Alan Stern wrote:
> Please don't top-post.
>
> On Fri, 7 Feb 2014, Zoran Markovic wrote:
>
> > I believe there may still be use cases where you want to wake up the
> > same CPU that scheduled the work.
>
> Won't the majority of cases not care which CPU is used? Therefore,
> shouldn't the default behavior be to use the power-efficient work
> queue?
>
> > Thanks for the Ack. Can you please queue this for 3.14?
>
> That's up to Greg KH. He may decide it's not important enough to go
> into 3.14, and delay it until 3.15.
It's 3.15 material, as it doesn't fix a regression at this point in
time.
I'll queue it up when I get to it in a week or so, thanks.
greg k-h
prev parent reply other threads:[~2014-02-07 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 3:16 Zoran Markovic
2014-02-02 16:10 ` Alan Stern
2014-02-07 12:03 ` Zoran Markovic
2014-02-07 15:20 ` Alan Stern
2014-02-07 15:28 ` Greg Kroah-Hartman [this message]
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=20140207152828.GA11557@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=burzalodowa@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=jwerner@chromium.org \
--cc=krzysiek@podlesie.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@beyermatthias.de \
--cc=mathias.nyman@linux.intel.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=shaibal.dutta@broadcom.com \
--cc=stern@rowland.harvard.edu \
--cc=thomas.pugliese@gmail.com \
--cc=zoran.markovic@linaro.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
Powered by JetHome