All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Jim Keniston <jkenisto@linux.vnet.ibm.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>,
	linux-kernel@vger.kernel.org,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 2/3] uprobes: fix 1-byte opcode tables
Date: Mon, 28 Jul 2014 17:25:17 +0200	[thread overview]
Message-ID: <20140728152517.GA15638@redhat.com> (raw)
In-Reply-To: <1404765773.4595.24.camel@oc7886638347.ibm.com.usor.ibm.com>

On 07/07, Jim Keniston wrote:
>
> I've at least verified that all your code changes are consistent with
> your comments.  Ditto for patch #3.
>
> Patches 1-3:
> Reviewed-by: Jim Keniston <jkenisto@us.ibm.com>

Sorry for delay.

I am going to apply this series. I'll ask to pull this later, probably
we willhave more changes.

Thanks Denys and Jim.

Oleg.


  reply	other threads:[~2014-07-28 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04 13:03 [PATCH 1/3] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Denys Vlasenko
2014-07-04 13:03 ` [PATCH 2/3] uprobes: fix 1-byte opcode tables Denys Vlasenko
2014-07-07 20:42   ` Jim Keniston
2014-07-28 15:25     ` Oleg Nesterov [this message]
2014-07-04 13:03 ` [PATCH 3/3] uprobe: fix 2-byte opcode table Denys Vlasenko
2014-07-07 17:12 ` [PATCH 1/3] uprobes: add comment with insn opcodes, mnemonics and why we dont support them Jim Keniston
2014-07-07 18:41   ` Denys Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2014-09-04 14:12 Denys Vlasenko
2014-09-04 14:12 ` [PATCH 2/3] uprobes: fix 1-byte opcode tables 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=20140728152517.GA15638@redhat.com \
    --to=oleg@redhat.com \
    --cc=dvlasenk@redhat.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --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 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.