[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohponvsL7BsabqkLS6W4EHx1N7=Ua04JwZksztPqwzW2ze=w@mail.gmail.com>
Date: Wed, 27 Feb 2013 20:44:52 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Tejun Heo <tj@...nel.org>
Cc: rjw@...k.pl, cpufreq@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org,
robin.randhawa@....com, Steve.Bannister@....com,
Liviu.Dudau@....com, charles.garcia-tobin@....com,
rickard.andersson@...ricsson.com, fabio.baltieri@...aro.org
Subject: Re: [PATCH 1/3] workqueue: define mod_scheduled_delayed_work[_on]() helpers
On 27 February 2013 20:40, Tejun Heo <tj@...nel.org> wrote:
> So, the intention is to just let people use system_wq. We no longer
> have single system-wide workqueue and we don't wanna add different
> variants matching each system wq. schedule_work() and friends were
> already there so I'm leaving those alone but I don't really want to
> add another set of rather meaningless wrappers. Please just use
> system_wq with mode_delayed_work*().
Even i thought the same initially but got these wrappers so that any updates
to workqueue used in schedule_work later on would simply work here as the
commiter would fix these too but fixing user drivers can be tricky.
To keep things aligned probably i should replace schedule_work() with
queue_work() and use system_wq there too..
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists