[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <561BACB8.7020405@redhat.com>
Date: Mon, 12 Oct 2015 14:51:04 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Dan Williams <dan.j.williams@...el.com>
Cc: "linux-nvdimm@...ts.01.org" <linux-nvdimm@...1.01.org>,
Dave Hansen <dave@...1.net>,
Russell King <linux@....linux.org.uk>,
Linux MM <linux-mm@...ck.org>, Gleb Natapov <gleb@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ralf Baechle <ralf@...ux-mips.org>,
Marc Zyngier <marc.zyngier@....com>,
Paul Mackerras <paulus@...ba.org>,
Christoffer Dall <christoffer.dall@...aro.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Christoph Hellwig <hch@....de>,
Alexander Graf <agraf@...e.com>, KVM list <kvm@...r.kernel.org>
Subject: Re: [PATCH v2 11/20] kvm: rename pfn_t to kvm_pfn_t
On 10/10/2015 22:57, Dan Williams wrote:
> On Sat, Oct 10, 2015 at 1:35 PM, Paolo Bonzini <pbonzini@...hat.com> wrote:
>> On 10/10/2015 02:56, Dan Williams wrote:
>>> The core has developed a need for a "pfn_t" type [1]. Move the existing
>>> pfn_t in KVM to kvm_pfn_t [2].
>>>
>>> [1]: https://lists.01.org/pipermail/linux-nvdimm/2015-September/002199.html
>>> [2]: https://lists.01.org/pipermail/linux-nvdimm/2015-September/002218.html
>>
>> Can you please change also the other types in include/linux/kvm_types.h?
>
> Hmm, all those seem kvm specific already. I'd only prefix them with
> kvm_ if they collided with a "core" type.
But they are all related and the code becomes uglier if you only prefix
one of them. If you don't convert all of them, I will do it anyway as
soon as this patch get in.
Since it touches a lot of KVM files, we should synchronize in order to
avoid conflicts and gnashing of teeth. What tree is this patch going
in? You could provide me a commit SHA1 for this patch (well, its
definitive version) based on Linus's tree (so that I can merge it in my
tree as well), or I could commit it and provide the SHA1 to the
maintainer of said tree.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists