mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:32:53 -0800	[thread overview]
Message-ID: <20130220003253.GA17414@htj.dyndns.org> (raw)
In-Reply-To: <20130220112709.cc28b5b07afd6475157bb6ad@canb.auug.org.au>

On Wed, Feb 20, 2013 at 11:27:09AM +1100, Stephen Rothwell wrote:
> >   $ 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 for checking - sorry for the noise.

And the other direction too just in case.

 $ git rev-list --pretty --oneline for-next ^for-3.9 ^for-3.9-cleanups ^for-3.9-async
 a4791ca Merge branch 'for-3.9' into for-next
 3b8d914 Merge branch 'for-3.9-cleanups' into for-next
 de16266 Merge branch 'for-3.9' into for-next
 3437170 Merge branch 'for-3.9' into for-next
 26c3d00 Merge branch 'for-3.9-cleanups' into for-next
 93883c9 Merge branch 'for-3.9-async' into for-next

So, yeah, they all match up.

Thanks for keeping an eye on it. :)

-- 
tejun

      reply	other threads:[~2013-02-20  0:32 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
2013-02-20  0:27         ` Stephen Rothwell
2013-02-20  0:32           ` Tejun Heo [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=20130220003253.GA17414@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®