netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: mgross@linux.intel.com
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
	aili@codeaurora.org, dwalker@codeaurora.org, tiwai@suse.de,
	bruce.w.allan@intel.com, davidb@quicinc.com, mcgrof@gmail.com,
	pavel@ucw.cz, "linux-pm" <linux-pm@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	NetDev <netdev@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Len Brown <lenb@kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH]PM QOS refresh against next-20100430
Date: Sat, 1 May 2010 01:08:28 +0200	[thread overview]
Message-ID: <201005010108.28593.rjw@sisk.pl> (raw)
In-Reply-To: <20100430230529.GA31391@linux.intel.com>

On Saturday 01 May 2010, mark gross wrote:
> On Sat, May 01, 2010 at 12:13:16AM +0200, Rafael J. Wysocki wrote:
> > On Friday 30 April 2010, mark gross wrote:
> > > The following is a refresh of the PM_QOS implementation, this patch
> > > updates some documentation input I got from Randy.
> > > 
> > > This patch changes the string based list management to a handle base
> > > implementation to help with the hot path use of pm-qos, it also renames
> > > much of the API to use "request" as opposed to "requirement" that was
> > > used in the initial implementation.  I did this because request more
> > > accurately represents what it actually does.
> > > 
> > > Also, I added a string based ABI for users wanting to use a string
> > > interface.  So if the user writes 0xDDDDDDDD formatted hex it will be
> > > accepted by the interface.  (someone asked me for it and I don't think
> > > it hurts anything.)
> > > 
> > > I really would like to get this refresh taken care of.  Its been taking
> > > me too long to close this.  please review or include it in next.
> > > 
> > > Thanks!
> > 
> > Well, I'd take it to suspend-2.6/linux-next, but first, it touches
> > subsystems whose maintainers were not in the Cc list, like the network
> > drivers, wireless and ACPI.  The changes are trivial, so I hope they don't
> > mind.
> > 
> > Second, my tree is based on the Linus' tree rather than linux-next and
> > the change in net/mac80211/scan.c doesn't seem to match that.  Please tell me
> > what I'm supposed to do about that.
> 
> You can waite for monday and I'll send a rebased version to linus' tree.
> 
> I thought linux-next was where folks wanted me to put it.
> 
> I'll email out a new one monday.

Great, thanks!

Rafael

  reply	other threads:[~2010-04-30 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100430212043.GA30315@linux.intel.com>
2010-04-30 22:13 ` [PATCH]PM QOS refresh against next-20100430 Rafael J. Wysocki
2010-04-30 23:05   ` mark gross
2010-04-30 23:08     ` Rafael J. Wysocki [this message]
2010-05-04 14:30       ` mark gross
2010-05-05 23:59         ` Rafael J. Wysocki

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=201005010108.28593.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=aili@codeaurora.org \
    --cc=bruce.w.allan@intel.com \
    --cc=davidb@quicinc.com \
    --cc=dwalker@codeaurora.org \
    --cc=johannes@sipsolutions.net \
    --cc=khilman@deeprootsystems.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=mgross@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=tiwai@suse.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 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).