From: Oleg Nesterov <oleg@redhat.com>
To: Denys Vlasenko <vda.linux@googlemail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jim Keniston <jkenisto@us.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/3] uprobes: add comment with insn opcodes, mnemonics and why we dont support them
Date: Fri, 5 Sep 2014 14:17:32 +0200 [thread overview]
Message-ID: <20140905121732.GA26662@redhat.com> (raw)
In-Reply-To: <CAK1hOcMM_79Uz=xms=BQu6BsrDLRmAaXUs_s-qOj-N0e-+qezA@mail.gmail.com>
On 09/05, Denys Vlasenko wrote:
>
> On Thu, Sep 4, 2014 at 4:24 PM, Oleg Nesterov <oleg@redhat.com> wrote:
> > Does this replace the previous series (which at first glance looks
> > pretty much the same) ?
>
> All 5 patches (two patch sets)
FYI, I obvoiuosly can't take the 1st series which changes lib/insn.c ;)
> I sent yesterday are resends.
OK, and the changes in arch/x86/kernel/uprobes.c (2nd series) were acked
by Jim in the past.
Oleg.
next prev parent reply other threads:[~2014-09-05 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 14:12 [PATCH 1/3] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Denys Vlasenko
2014-09-04 14:12 ` [PATCH 2/3] uprobes: fix 1-byte opcode tables Denys Vlasenko
2014-09-04 14:12 ` [PATCH 3/3] uprobe: fix 2-byte opcode table Denys Vlasenko
2014-09-04 14:24 ` [PATCH 1/3] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Oleg Nesterov
2014-09-05 12:10 ` Denys Vlasenko
2014-09-05 12:17 ` Oleg Nesterov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-04 13:03 Denys Vlasenko
2014-07-07 17:12 ` Jim Keniston
2014-07-07 18:41 ` Denys Vlasenko
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=20140905121732.GA26662@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=vda.linux@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.