public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: lkml <linux-kernel@vger.kernel.org>, Oleg Nesterov <oleg@redhat.com>
Subject: ptrace pull request for linux-next
Date: Tue, 29 Mar 2011 11:02:48 +0200	[thread overview]
Message-ID: <20110329090248.GJ6736@htj.dyndns.org> (raw)

Hello, Stephen.

Can you please pull from the following tree into linux-next?

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git ptrace

The tree hosts ongoing ptrace/group stop improvements.  Oleg is in the
process of getting a korg account and setting up a dedicated tree and
it has been agreed that I maintain a temporary tree to be tested in
linux-next until things are properly setup.  The branch is stable and
will be pulled verbatim into Oleg's tree once it's up and running.

Thank you.

-- 
tejun

             reply	other threads:[~2011-03-29  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  9:02 Tejun Heo [this message]
2011-03-29 23:12 ` ptrace pull request for linux-next Stephen Rothwell
2011-05-10 12:24   ` Oleg Nesterov
2011-05-11  0:06     ` Stephen Rothwell

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=20110329090248.GJ6736@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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