public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, weidong.han@intel.com,
	mingo@redhat.com, dwmw2@infradead.org, amit.shah@redhat.com
Subject: Re: [PATCH 1/9] KVM: rename vtd.c to iommu.c
Date: Thu, 27 Nov 2008 18:32:56 +0200	[thread overview]
Message-ID: <492ECBB8.6070509@redhat.com> (raw)
In-Reply-To: <1227800454-9555-2-git-send-email-joerg.roedel@amd.com>

Joerg Roedel wrote:
> Impace: file renamed
>
>   

"impact"?

> The code in the vtd.c file can be reused for other IOMMUs as well. So
> rename it to make it clear that it handle more than VT-d.
>
> Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
> ---
>  arch/ia64/kvm/Makefile |    2 +-
>  arch/x86/kvm/Makefile  |    2 +-
>  virt/kvm/iommu.c       |  191 ++++++++++++++++++++++++++++++++++++++++++++++++
>  virt/kvm/vtd.c         |  191 ------------------------------------------------
>   

Use the git -M switch, which show renames as renames instead of 
removes+adds.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-11-27 16:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 15:40 [PATCH 0/9] Factor VT-d KVM functions into a generic API Joerg Roedel
2008-11-27 15:40 ` [PATCH 1/9] KVM: rename vtd.c to iommu.c Joerg Roedel
2008-11-27 16:32   ` Avi Kivity [this message]
2008-11-27 17:05     ` Joerg Roedel
2008-11-30 10:12       ` Avi Kivity
2008-11-27 15:40 ` [PATCH 2/9] introcude linux/iommu.h for an iommu api Joerg Roedel
2008-11-28  2:50   ` Han, Weidong
2008-11-27 15:40 ` [PATCH 3/9] add frontend implementation for the IOMMU API Joerg Roedel
2008-11-28  2:50   ` Han, Weidong
2008-12-01 18:16     ` 'Joerg Roedel'
2008-11-28  9:40   ` FUJITA Tomonori
2008-11-28 11:31     ` Joerg Roedel
2008-12-01  8:38       ` FUJITA Tomonori
2008-12-01 12:00         ` Joerg Roedel
2008-12-01 13:02           ` Muli Ben-Yehuda
2008-12-01 14:07             ` Joerg Roedel
2008-12-01 14:18             ` FUJITA Tomonori
2008-12-01 14:27               ` Joerg Roedel
2008-12-01 14:33                 ` Avi Kivity
2008-12-01 15:46                   ` Joerg Roedel
2008-12-01 15:58                   ` FUJITA Tomonori
2008-12-01 16:59                     ` Joerg Roedel
2008-12-01 17:27                     ` Joerg Roedel
2008-11-27 15:40 ` [PATCH 4/9] select IOMMU_API when DMAR and/or AMD_IOMMU is selected Joerg Roedel
2008-11-27 15:40 ` [PATCH 5/9] VT-d: add domain init and destroy functions for IOMMU API Joerg Roedel
2008-11-27 15:40 ` [PATCH 6/9] VT-d: add device attach and detach " Joerg Roedel
2008-11-27 15:40 ` [PATCH 7/9] VT-d: add domain map and iova_to_phys " Joerg Roedel
2008-11-27 15:40 ` [PATCH 8/9] VT-d: register functions for the " Joerg Roedel
2008-11-28  2:50   ` Han, Weidong
2008-11-27 15:40 ` [PATCH 9/9] KVM: change KVM iommu.c to use " Joerg Roedel
2008-11-27 15:43 ` [osrc-patches] [PATCH 0/9] Factor VT-d KVM functions into a generic API Joerg Roedel

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=492ECBB8.6070509@redhat.com \
    --to=avi@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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