From: Daniel Walker <dwalker@codeaurora.org>
To: David Brown <davidb@codeaurora.org>
Cc: Tejun Heo <tj@kernel.org>,
Stanislaw Gruszka <sgruszka@redhat.com>,
linux-kernel@vger.kernel.org, Stanislaw Gruszka <stf_xl@wp.pl>,
linux-usb@vger.kernel.org, Bryan Huntsman <bryanh@codeaurora.org>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 20/32] video/msm_fb: use system_wq instead of dedicated workqueues
Date: Tue, 25 Jan 2011 11:16:16 -0800 [thread overview]
Message-ID: <1295982976.25496.29.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <8ya7hdsg5j0.fsf@huya.qualcomm.com>
On Tue, 2011-01-25 at 11:14 -0800, David Brown wrote:
> On Tue, Jan 25 2011, Daniel Walker wrote:
>
> > On Tue, 2011-01-25 at 14:45 +0100, Tejun Heo wrote:
> >> On Mon, Jan 03, 2011 at 10:10:45AM -0800, Daniel Walker wrote:
> >> > On Mon, 2011-01-03 at 18:06 +0100, Stanislaw Gruszka wrote:
> >> > > On Mon, Jan 03, 2011 at 02:49:43PM +0100, Tejun Heo wrote:
> >> > > > With cmwq, there's no reason to use separate workqueues. Drop
> >> > > > msmfb_info->resume_workqueue and use system_wq instead.
> >> > > >
> >> > > > Signed-off-by: Tejun Heo <tj@kernel.org>
> >> > > > Cc: Stanislaw Gruszka <stf_xl@wp.pl>
> >> > > I'm not the right person, CC according to MAINTAINERS
> >> >
> >> > ARM/QUALCOMM MSM MACHINE SUPPORT
> >> > M: David Brown <davidb@codeaurora.org>
> >> > M: Daniel Walker <dwalker@codeaurora.org>
> >> > M: Bryan Huntsman <bryanh@codeaurora.org>
> >>
> >> Oops, sorry about that. So how does the patch look? Are you gonna
> >> take it through msm tree or shall I take it?
> >
> > David ?
> >
> > Daniel
>
> Is it difficult for you to test this change, Daniel? I can pull it in
> once we verify it still works.
Carl V. can test it, and review it I think ..
Daniel
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-01-25 19:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1294062595-30097-1-git-send-email-tj@kernel.org>
[not found] ` <1294062595-30097-21-git-send-email-tj@kernel.org>
[not found] ` <1294062595-30097-21-git-send-email-tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2011-01-03 17:06 ` [PATCH 20/32] video/msm_fb: use system_wq instead of dedicated workqueues Stanislaw Gruszka
[not found] ` <20110103170615.GB2285-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-01-03 18:10 ` Daniel Walker
[not found] ` <1294078245.18295.5.camel-y5Owza0q8UhBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2011-01-25 13:45 ` Tejun Heo
[not found] ` <20110125134558.GY27510-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2011-01-25 18:00 ` Daniel Walker
2011-01-25 19:14 ` David Brown
2011-01-25 19:16 ` Daniel Walker [this message]
[not found] ` <1295982976.25496.29.camel-y5Owza0q8UhBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2011-01-25 22:08 ` Carl Vanderlip
2011-01-25 23:21 ` David Brown
2011-01-26 10:41 ` Tejun Heo
2011-01-26 18:04 ` David Brown
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=1295982976.25496.29.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=stf_xl@wp.pl \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).