From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: Re: [GIT PULL UPDATED] workqueue core changes for 3.9-rc1
Date: Tue, 19 Feb 2013 16:19:25 -0800 [thread overview]
Message-ID: <20130220001925.GZ17414@htj.dyndns.org> (raw)
In-Reply-To: <20130220111413.b9444b48400f808d8921be89@canb.auug.org.au>
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@canb.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
next prev parent reply other threads:[~2013-02-20 0:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 17:39 [GIT PULL] " Tejun Heo
2013-02-19 18:13 ` [GIT PULL UPDATED] " Tejun Heo
2013-02-20 0:11 ` Stephen Rothwell
2013-02-20 0:14 ` Stephen Rothwell
2013-02-20 0:19 ` Tejun Heo [this message]
2013-02-20 0:27 ` Stephen Rothwell
2013-02-20 0:32 ` Tejun Heo
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=20130220001925.GZ17414@htj.dyndns.org \
--to=tj@kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®