All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nakajima, Jun" <jun.nakajima@intel.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH v3 01/13] nEPT: Support LOAD_IA32_EFER entry/exit controls for L1
Date: Sat, 18 May 2013 21:57:35 -0700	[thread overview]
Message-ID: <CAL54oT3JxzcxF3VE=afPg3+k9tZh7qWFWs1bChw=t-PLm1Q9vQ@mail.gmail.com> (raw)
In-Reply-To: <20130513122520.GR10830@redhat.com>

On Mon, May 13, 2013 at 5:25 AM, Gleb Natapov <gleb@redhat.com> wrote:
> Please use --no-chain-reply-to option to "git send-email" for nicer
> email threading and there is something wrong with Signed-off chain for
> the patches. The first Signed-off-by: is by Nadav, but you appears to be
> the author of the patches for git. AFAIK Nadav is the author, so you
> need to add proper From: in your patch submission. If you'll fix the
> authorship in your git "git format-patch" will do it for you.

I have been out of town, and I just have re-submitted v3 patches,
using the options. I wrote the patches 12/13 and 13/13, so I didn't
add From: Nadav in them.

--
Jun
Intel Open Source Technology Center

  reply	other threads:[~2013-05-19  4:57 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  0:53 [PATCH v3 01/13] nEPT: Support LOAD_IA32_EFER entry/exit controls for L1 Jun Nakajima
2013-05-09  0:53 ` [PATCH v3 02/13] nEPT: Move gpte_access() and prefetch_invalid_gpte() to paging_tmpl.h Jun Nakajima
2013-05-09  0:53   ` [PATCH v3 03/13] nEPT: Add EPT tables support " Jun Nakajima
2013-05-09  0:53     ` [PATCH v3 04/13] nEPT: Define EPT-specific link_shadow_page() Jun Nakajima
2013-05-09  0:53       ` [PATCH v3 05/13] nEPT: MMU context for nested EPT Jun Nakajima
2013-05-09  0:53         ` [PATCH v3 06/13] nEPT: Fix cr3 handling in nested exit and entry Jun Nakajima
2013-05-09  0:53           ` [PATCH v3 07/13] nEPT: Fix wrong test in kvm_set_cr3 Jun Nakajima
2013-05-09  0:53             ` [PATCH v3 08/13] nEPT: Some additional comments Jun Nakajima
2013-05-09  0:53               ` [PATCH v3 09/13] nEPT: Advertise EPT to L1 Jun Nakajima
2013-05-09  0:53                 ` [PATCH v3 10/13] nEPT: Nested INVEPT Jun Nakajima
2013-05-09  0:53                   ` [PATCH v3 11/13] nEPT: Miscelleneous cleanups Jun Nakajima
2013-05-09  0:53                     ` [PATCH v3 12/13] nEPT: Move is_rsvd_bits_set() to paging_tmpl.h Jun Nakajima
2013-05-09  0:53                       ` [PATCH v3 13/13] nEPT: Inject EPT violation/misconfigration Jun Nakajima
2013-05-14 12:41                         ` Paolo Bonzini
2013-05-13 12:25 ` [PATCH v3 01/13] nEPT: Support LOAD_IA32_EFER entry/exit controls for L1 Gleb Natapov
2013-05-19  4:57   ` Nakajima, Jun [this message]
2013-05-19  4:52 Jun Nakajima
2013-05-20 12:33 ` Paolo Bonzini
2013-07-02  3:01   ` Zhang, Yang Z
2013-07-02 13:59     ` Gleb Natapov
2013-07-02 14:28       ` Jan Kiszka
2013-07-02 15:15         ` Gleb Natapov
2013-07-02 15:34           ` Jan Kiszka
2013-07-02 15:43             ` Gleb Natapov
2013-07-04  8:42               ` Zhang, Yang Z
2013-07-08 12:37                 ` Gleb Natapov
2013-07-08 14:28                   ` Zhang, Yang Z
2013-07-08 16:08                     ` Gleb Natapov

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='CAL54oT3JxzcxF3VE=afPg3+k9tZh7qWFWs1bChw=t-PLm1Q9vQ@mail.gmail.com' \
    --to=jun.nakajima@intel.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.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 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.