From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: "Bhaktipriya Shridhar" <bhaktipriya96@gmail.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Pali Rohár" <pali.rohar@gmail.com>,
"Chris Diamand" <chris@diamand.org>,
"Stefan Assmann" <sassmann@kpanic.de>,
"Richard Pospesel" <pospeselr@gmail.com>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Takashi Iwai" <tiwai@suse.de>,
patches@opensource.wolfsonmicro.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Input: psmouse: Remove deprecated create_singletheread_workqueue
Date: Tue, 23 Aug 2016 13:51:22 -0700 [thread overview]
Message-ID: <20160823205122.GD6712@dtor-ws> (raw)
In-Reply-To: <20160815225345.GC3672@mtj.duckdns.org>
On Mon, Aug 15, 2016 at 06:53:45PM -0400, Tejun Heo wrote:
> On Sun, Aug 14, 2016 at 10:53:07AM +0530, Bhaktipriya Shridhar wrote:
> > alloc_ordered_workqueue replaces the deprecated
> > create_singlethread_workqueue.
> >
> > There are multiple work items on the work queue viz
> > &priv->dev3_register_work, &priv->recalib_wq, &psmouse->resync_work,
> > which require execution ordering. Hence, an ordered workqueue has been
> > used.
> >
> > The workqueue is not being used on a memory reclaim path.
> > Hence, WQ_MEM_RECLAIM has not been set.
> >
> > Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
>
> Acked-by: Tejun Heo <tj@kernel.org>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2016-08-23 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 5:19 [PATCH 0/3] Remove usages of deprecated create_singlethread_workqueue Bhaktipriya Shridhar
2016-08-14 5:23 ` [PATCH 1/3] Input: psmouse: Remove deprecated create_singletheread_workqueue Bhaktipriya Shridhar
2016-08-15 22:53 ` Tejun Heo
2016-08-23 20:51 ` Dmitry Torokhov [this message]
2016-08-14 5:25 ` [PATCH 2/3] Input: touchscreen: mc13783_ts: " Bhaktipriya Shridhar
2016-08-15 22:53 ` Tejun Heo
2016-08-23 20:53 ` Dmitry Torokhov
2016-08-14 5:26 ` [PATCH 3/3] Input: wm97xx: " Bhaktipriya Shridhar
2016-08-15 8:53 ` Charles Keepax
2016-08-15 22:53 ` Tejun Heo
2016-08-23 21:01 ` Dmitry Torokhov
2016-08-23 21:02 ` Dmitry Torokhov
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=20160823205122.GD6712@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=bhaktipriya96@gmail.com \
--cc=chris@diamand.org \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=pospeselr@gmail.com \
--cc=sassmann@kpanic.de \
--cc=tiwai@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.