kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wu, Feng" <feng.wu@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Christoffer Dall <cdall@cs.columbia.edu>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Cornelia Huck <cornelia.huck@de.ibm.com>,
	"Wu, Feng" <feng.wu@intel.com>
Subject: RE: linux-next: manual merge of the kvm-arm tree with the kvm tree
Date: Fri, 16 Oct 2015 04:20:16 +0000	[thread overview]
Message-ID: <E959C4978C3B6342920538CF579893F00ADDDC19@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20151016145300.7f03fbcb@canb.auug.org.au>



> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Friday, October 16, 2015 11:53 AM
> To: Christoffer Dall <cdall@cs.columbia.edu>; Marc Zyngier
> <marc.zyngier@arm.com>; Marcelo Tosatti <mtosatti@redhat.com>; Gleb
> Natapov <gleb@kernel.org>; kvm@vger.kernel.org
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Wu, Feng
> <feng.wu@intel.com>; Paolo Bonzini <pbonzini@redhat.com>; Christian
> Borntraeger <borntraeger@de.ibm.com>; Cornelia Huck
> <cornelia.huck@de.ibm.com>
> Subject: linux-next: manual merge of the kvm-arm tree with the kvm tree
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).

Thanks Stephen!

Thanks,
Feng

  reply	other threads:[~2015-10-16  4:20 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  3:53 linux-next: manual merge of the kvm-arm tree with the kvm tree Stephen Rothwell
2015-10-16  4:20 ` Wu, Feng [this message]
2016-07-20  5:27 Stephen Rothwell
2016-07-24  5:59 Stephen Rothwell
2016-07-24  6:04 Stephen Rothwell
2017-04-10  3:52 Stephen Rothwell
2017-04-10  6:26 ` Christoffer Dall
2018-10-18  2:46 Stephen Rothwell
2020-03-25  3:23 Stephen Rothwell
2020-07-13  4:39 Stephen Rothwell
2020-08-09  8:54 ` Stephen Rothwell
2020-07-13  4:40 Stephen Rothwell
2020-08-09  8:55 ` Stephen Rothwell
2021-04-22  4:39 Stephen Rothwell
2021-04-22  4:43 Stephen Rothwell
2021-06-22  5:31 Stephen Rothwell
2021-06-23  5:53 Stephen Rothwell
2021-06-25  5:15 Stephen Rothwell
2021-06-25  5:20 Stephen Rothwell
2021-06-25  5:24 Stephen Rothwell
2021-12-17  4:19 Stephen Rothwell
2022-05-05  4:47 Stephen Rothwell
2022-07-18  5:19 Stephen Rothwell
2022-12-01  0:24 Stephen Rothwell
2022-12-01  0:57 Stephen Rothwell
2022-12-01  1:09 Stephen Rothwell
2022-12-01  2:16 Stephen Rothwell
2022-12-01 15:23 ` Marc Zyngier
2023-03-31  2:26 Stephen Rothwell
2023-04-06  3:06 Stephen Rothwell

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=E959C4978C3B6342920538CF579893F00ADDDC19@SHSMSX104.ccr.corp.intel.com \
    --to=feng.wu@intel.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cdall@cs.columbia.edu \
    --cc=cornelia.huck@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=sfr@canb.auug.org.au \
    /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).