From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: mgross@linux.intel.com
Cc: Pavel Machek <pavel@ucw.cz>, 640E9920 <640e9920@gmail.com>,
linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, dwalker@codeaurora.org,
tiwai@suse.de, bruce.w.allan@intel.com, aili@codeaurora.org,
khilman@deeprootsystems.com
Subject: Re: [PATCH] PM_QOS updates for 2.6.34-rc1
Date: Fri, 19 Mar 2010 20:49:34 +0100 [thread overview]
Message-ID: <201003192049.34665.rjw@sisk.pl> (raw)
In-Reply-To: <20100319143055.GA6124@linux.intel.com>
On Friday 19 March 2010, mark gross wrote:
> On Sun, Mar 14, 2010 at 07:26:37AM +0100, Pavel Machek wrote:
> > On Sat 2010-03-13 16:34:25, 640E9920 wrote:
> > > The following patch series implements to following:
> > > 1) pm_qos now uses a handle based implementation. No more string
> > > compares while walking lists.
> > > 2) renames the exports to using more accurate names.
> > > 3) updates kernel clients of pm_qos per this change
> > > 4) added ascii interface to pmqos recognizing strings formatted in 10
> > > charactor format "0x12345678"
> > > 5) added new pm_qos class, "system_bus_throughput"
> > >
> > > I would like to see this series make it into 2.6.34 if its not too late.
> >
> > I believe it is... -rc1 is past us.
>
> crap. I'll guess I'll redo them for next then.
>
>
>
> > Also... the way the patches are structured... that will break bisect,
> > no?
>
> Um not sure, how would you recomend I structure them?
Generally speaking, the kernel should build and should work correctly after
applying each consecutive patch in the series.
Rafael
next prev parent reply other threads:[~2010-03-19 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 0:34 [PATCH] PM_QOS updates for 2.6.34-rc1 640E9920
2010-03-14 6:26 ` Pavel Machek
2010-03-14 20:08 ` Rafael J. Wysocki
2010-03-19 14:30 ` mark gross
2010-03-19 19:49 ` Rafael J. Wysocki [this message]
2010-03-19 19:52 ` Daniel Walker
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=201003192049.34665.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=640e9920@gmail.com \
--cc=aili@codeaurora.org \
--cc=bruce.w.allan@intel.com \
--cc=dwalker@codeaurora.org \
--cc=khilman@deeprootsystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mgross@linux.intel.com \
--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