[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190401142026.GA2792@sasha-vm>
Date: Mon, 1 Apr 2019 10:20:26 -0400
From: Sasha Levin <sashal@...nel.org>
To: Mukesh Ojha <mojha@...eaurora.org>
Cc: lantianyu1986@...il.com, davem@...emloft.net,
mchehab+samsung@...nel.org, gregkh@...uxfoundation.org,
nicolas.ferre@...rochip.com, tglx@...utronix.de, mingo@...nel.org,
konrad.wilk@...cle.com, jpoimboe@...hat.com, peterz@...radead.org,
jkosina@...e.cz, riel@...riel.com, peterz@...raded.org,
Tianyu.Lan@...rosoft.com, luto@...nel.org,
michael.h.kelley@...rosoft.com, kys@...rosoft.com, joe@...ches.com,
linux-kernel@...r.kernel.org, linux-hyperv@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Fix Hyperv vIOMMU driver file name
On Tue, Mar 26, 2019 at 02:57:09PM +0530, Mukesh Ojha wrote:
>
>On 3/26/2019 11:58 AM, lantianyu1986@...il.com wrote:
>>From: Lan Tianyu <Tianyu.Lan@...rosoft.com>
>>
>>The Hyperv vIOMMU file name should be "hyperv-iommu.c" rather
>
>s/vIOMMU/IOMMU
What's wrong with vIOMMU? There's no hardware involved (afaik).
--
Thanks,
Sasha
Powered by blists - more mailing lists