linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: lantianyu1986@gmail.com, davem@davemloft.net,
	mchehab+samsung@kernel.org, gregkh@linuxfoundation.org,
	nicolas.ferre@microchip.com, tglx@linutronix.de,
	mingo@kernel.org, konrad.wilk@oracle.com, jpoimboe@redhat.com,
	peterz@infradead.org, jkosina@suse.cz, riel@surriel.com,
	peterz@infraded.org, Tianyu.Lan@microsoft.com, luto@kernel.org,
	michael.h.kelley@microsoft.com, kys@microsoft.com,
	joe@perches.com, linux-kernel@vger.kernel.org,
	linux-hyperv@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Fix Hyperv vIOMMU driver file name
Date: Mon, 1 Apr 2019 10:20:26 -0400	[thread overview]
Message-ID: <20190401142026.GA2792@sasha-vm> (raw)
In-Reply-To: <58c16b52-5833-ede0-c4b0-8b8839ef06b2@codeaurora.org>

On Tue, Mar 26, 2019 at 02:57:09PM +0530, Mukesh Ojha wrote:
>
>On 3/26/2019 11:58 AM, lantianyu1986@gmail.com wrote:
>>From: Lan Tianyu <Tianyu.Lan@microsoft.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

  parent reply	other threads:[~2019-04-01 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26  6:28 [PATCH] MAINTAINERS: Fix Hyperv vIOMMU driver file name lantianyu1986
2019-03-27 13:51 ` Mukesh Ojha
2019-03-27 14:09 ` Mukesh Ojha
     [not found] ` <58c16b52-5833-ede0-c4b0-8b8839ef06b2@codeaurora.org>
2019-04-01 14:20   ` Sasha Levin [this message]
2019-04-01 15:01     ` Mukesh Ojha

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=20190401142026.GA2792@sasha-vm \
    --to=sashal@kernel.org \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=joe@perches.com \
    --cc=jpoimboe@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kys@microsoft.com \
    --cc=lantianyu1986@gmail.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=michael.h.kelley@microsoft.com \
    --cc=mingo@kernel.org \
    --cc=mojha@codeaurora.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=peterz@infradead.org \
    --cc=peterz@infraded.org \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    /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).