All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yang, Sheng" <sheng.yang@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 0/2] Clean up for MSR_IA32_FEATURE_CONTROL
Date: Thu, 11 Sep 2008 15:05:07 +0800	[thread overview]
Message-ID: <200809111505.07875.sheng.yang@intel.com> (raw)
In-Reply-To: <20080911063523.GA27877@elte.hu>

On Thursday 11 September 2008 14:35:23 Ingo Molnar wrote:
> * Sheng Yang <sheng.yang@intel.com> wrote:
> > Hi, Ingo
> >
> > Here is some follow up clean up for "Move VMX MSRs to msr-index.h".
> > After discussion with Avi, I found it's more proper to move
> > MSR_IA32_FEATURE_CONTROL bits to msr-index.h as well.
> >
> > But I got a little puzzle about where to accept these patches. I
> > suppose these can be picked up by tip then go with kvm when it merge
> > upstream? The main problem is macro name changed to keep consistent
> > style.
>
> there's a few changes pending for that file:
>
>   earth4:~/tip> gll linus.. include/asm-x86/msr-index.h
>   315a655: x86: move VMX MSRs to msr-index.h
>   77ef50a: x86: consolidate header guards
>
> so i guess best is to put 315a655 into kvm.git as well and do these
> changes there. The header-guard changes should not cause significant
> merge trouble.
>

OK, I will resend the patches to KVM mailing list(o, forgot to CC them 
here...)

Thanks!

-- 
regards
Yang, Sheng


> 	Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



      reply	other threads:[~2008-09-11  7:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11  2:33 [PATCH 0/2] Clean up for MSR_IA32_FEATURE_CONTROL Sheng Yang
2008-09-11  6:35 ` Ingo Molnar
2008-09-11  7:05   ` Yang, Sheng [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=200809111505.07875.sheng.yang@intel.com \
    --to=sheng.yang@intel.com \
    --cc=avi@qumranet.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.