From: Daniel Vetter <daniel@ffwll.ch>
To: Tejun Heo <tj@kernel.org>
Cc: Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] i915: use alloc_ordered_workqueue() instead of explicit UNBOUND w/ max_active = 1
Date: Fri, 24 Aug 2012 01:14:10 +0200 [thread overview]
Message-ID: <20120823231410.GF5418@phenom.ffwll.local> (raw)
In-Reply-To: <20120823192227.GB14962@google.com>
On Thu, Aug 23, 2012 at 12:22:27PM -0700, Tejun Heo wrote:
> Hello,
>
> On Thu, Aug 23, 2012 at 10:43:25AM +0200, Daniel Vetter wrote:
> > On Thu, Aug 23, 2012 at 08:56:37AM +0100, Chris Wilson wrote:
> > > On Wed, 22 Aug 2012 16:40:57 -0700, Tejun Heo <tj@kernel.org> wrote:
> > > > This is an equivalent conversion and will ease scheduled removal of
> > > > WQ_NON_REENTRANT.
> > > >
> > > > Signed-off-by: Tejun Heo <tj@kernel.org>
> > > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch> for merging through any
> > tree that pleases you (if it makes merging easier for WQ_NON_REENTRANT
> > removal). Or should I just merge this through drm-intel-next?
>
> I think it would be better to route this one through drm-intel-next.
> WQ_NON_REENTRANT won't be deprecated until after the next -rc1 anyway.
Queued for -next, thanks for the patch.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
prev parent reply other threads:[~2012-08-23 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 23:40 [PATCH] i915: use alloc_ordered_workqueue() instead of explicit UNBOUND w/ max_active = 1 Tejun Heo
2012-08-23 7:56 ` Chris Wilson
2012-08-23 8:43 ` Daniel Vetter
2012-08-23 19:22 ` Tejun Heo
2012-08-23 23:14 ` Daniel Vetter [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=20120823231410.GF5418@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--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