public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: 'Joerg Roedel' <joerg.roedel@amd.com>,
	"Woodhouse, David" <david.woodhouse@intel.com>,
	'Jesse Barnes' <jbarnes@virtuousgeek.org>,
	'Avi Kivity' <avi@redhat.com>,
	"Kay, Allen M" <allen.m.kay@intel.com>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>,
	"'iommu@lists.linux-foundation.org'"
	<iommu@lists.linux-foundation.org>
Subject: Re: [PATCH 1/2] [v2] VT-d: Support multiple device assignment for KVM
Date: Mon, 1 Dec 2008 15:04:10 +0100	[thread overview]
Message-ID: <20081201140410.GB24323@8bytes.org> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C018BF0557C@pdsmsx503.ccr.corp.intel.com>

Ok, I got them to apply. I also did the checkpatch cleanups. To speed
things up a bit I would suggest that I rebase my patchset on your
patches and send it out in a single series. Any problems with this
approach?

Joerg

On Mon, Dec 01, 2008 at 09:22:42PM +0800, Han, Weidong wrote:
> Sorry, this patch has style problem. I will update it and also split it to smaller patches for easy reviewing.
> 
> Regards,
> Weidong
> 
> 'Joerg Roedel' wrote:
> > Hmm, I get these errors using git-am:
> > 
> > Applying VT-d: Support multiple device assignment for KVM
> > .dotest/patch:1344: space before tab in indent.
> >                                 clflush_cache_range(addr, size);
> > .dotest/patch:1350: space before tab in indent.
> >                         clflush_cache_range(addr, size);
> > .dotest/patch:1907: trailing whitespace.
> > 
> > .dotest/patch:1946: trailing whitespace.
> >                  * owned by this domain, clear this iommu in iommu_bmp
> > .dotest/patch:2300: trailing whitespace.
> > 
> > error: patch failed: drivers/pci/dmar.c:484
> > error: drivers/pci/dmar.c: patch does not apply
> > error: patch failed: drivers/pci/intel-iommu.c:50
> > error: drivers/pci/intel-iommu.c: patch does not apply
> > error: patch failed: include/linux/dma_remapping.h:111
> > error: include/linux/dma_remapping.h: patch does not apply
> > error: patch failed: include/linux/intel-iommu.h:219
> > error: include/linux/intel-iommu.h: patch does not apply
> > Patch failed at 0001.
> > 
> > Joerg
> > 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-12-01 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 13:49 [PATCH 1/2] [v2] VT-d: Support multiple device assignment for KVM Han, Weidong
2008-11-28 13:27 ` Joerg Roedel
2008-12-01  6:17   ` Han, Weidong
2008-12-01 11:55     ` 'Joerg Roedel'
2008-12-01 13:22       ` Han, Weidong
2008-12-01 14:04         ` Joerg Roedel [this message]
2008-12-02  0:31           ` Han, Weidong

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=20081201140410.GB24323@8bytes.org \
    --to=joro@8bytes.org \
    --cc=allen.m.kay@intel.com \
    --cc=avi@redhat.com \
    --cc=david.woodhouse@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=weidong.han@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox