From: Ingo Molnar <mingo@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, Anton Arapov <aarapov@redhat.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] uprobes: uprobe_copy_process() and copy_insn() fixes
Date: Mon, 11 Nov 2013 09:46:02 +0100 [thread overview]
Message-ID: <20131111084602.GD12405@gmail.com> (raw)
In-Reply-To: <20131109161857.GA17484@redhat.com>
* Oleg Nesterov <oleg@redhat.com> wrote:
> Ingo, please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
Pulled, thanks a lot Oleg!
> I do not like to spam you, but I think that at least the 1st patch
> should be merged now, along with other retprobe && fork fixed.
It's not possible for you to spam me with patches! :-)
Thanks,
Ingo
prev parent reply other threads:[~2013-11-11 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 16:18 [GIT PULL] uprobes: uprobe_copy_process() and copy_insn() fixes Oleg Nesterov
2013-11-11 8:46 ` Ingo Molnar [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=20131111084602.GD12405@gmail.com \
--to=mingo@kernel.org \
--cc=aarapov@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=srikar@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).