[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130220001925.GZ17414@htj.dyndns.org>
Date: Tue, 19 Feb 2013 16:19:25 -0800
From: Tejun Heo <tj@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Lai Jiangshan <laijs@...fujitsu.com>
Subject: Re: [GIT PULL UPDATED] workqueue core changes for 3.9-rc1
On Wed, Feb 20, 2013 at 11:14:13AM +1100, Stephen Rothwell wrote:
> HI Tejun,
>
> On Wed, 20 Feb 2013 11:11:25 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > This is very different from what has been in linux-next (it looks like
> > you have been cherry-picking fixes from other sources into your for-next
> > branch?):
>
> Or maybe what is in linux-next is a mash up of several different things?
Ooh, wq/for-next was combination of wq/for-3.9, wq/for-3.9-cleanups
and wq/for-3.9-async. I'm fairly sure all the commits are accounted
for. Checking again just in case....
$ git rev-list --pretty --oneline tmp ^next-20130219
bd26f12 Merge branch 'for-3.9-async' into tmp
0f985c9 Merge branch 'for-3.9-cleanups' into tmp
1438ade5 workqueue: un-GPL function delayed_work_timer_fn()
tmp is for-3.9 + for-3.9-async + for-3.9-cleanups, so yeah other than
the last cherry-pick, everything seems to be in order.
Thanks.
--
tejun
--
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