From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Easwar Hariharan <eahariha@linux.microsoft.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Wei Liu" <wei.liu@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"open list:Hyper-V/Azure CORE AND DRIVERS"
<linux-hyperv@vger.kernel.org>,
"open list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
<linux-pci@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
Hyper-V/Azure@thinkpad, CORE@thinkpad, AND@thinkpad,
DRIVERS@thinkpad, status: Supported@thinkpad, PCI@thinkpad,
NATIVE@thinkpad, HOST@thinkpad, BRIDGE@thinkpad,
ENDPOINT@thinkpad, SUBSYSTEM@thinkpad;
Subject: Re: [PATCH v2] PCI: hv: Correct a comment
Date: Mon, 10 Feb 2025 23:22:58 +0530 [thread overview]
Message-ID: <20250210175258.pwaqr3dqxstcjmui@thinkpad> (raw)
In-Reply-To: <20250207190716.89995-1-eahariha@linux.microsoft.com>
On Fri, Feb 07, 2025 at 07:07:15PM +0000, Easwar Hariharan wrote:
> The VF driver controls an endpoint attached to the pci-hyperv
> controller. An invalidation sent by the PF driver in the host would be
> delivered *to* the endpoint driver by the controller driver.
>
> Signed-off-by: Easwar Hariharan <eahariha@linux.microsoft.com>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
Where is the changelog?
- Mani
> drivers/pci/controller/pci-hyperv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pci/controller/pci-hyperv.c b/drivers/pci/controller/pci-hyperv.c
> index 6084b38bdda1..3ae3a8a79dcf 100644
> --- a/drivers/pci/controller/pci-hyperv.c
> +++ b/drivers/pci/controller/pci-hyperv.c
> @@ -1356,7 +1356,7 @@ static struct pci_ops hv_pcifront_ops = {
> *
> * If the PF driver wishes to initiate communication, it can "invalidate" one or
> * more of the first 64 blocks. This invalidation is delivered via a callback
> - * supplied by the VF driver by this driver.
> + * supplied to the VF driver by this driver.
> *
> * No protocol is implied, except that supplied by the PF and VF drivers.
> */
> --
> 2.43.0
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-02-10 17:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 19:07 [PATCH v2] PCI: hv: Correct a comment Easwar Hariharan
2025-02-08 15:45 ` Michael Kelley
2025-02-10 17:52 ` Manivannan Sadhasivam [this message]
2025-02-10 18:16 ` Easwar Hariharan
2025-02-12 2:24 ` Wei Liu
2025-02-20 15:09 ` Krzysztof Wilczyński
2025-02-21 19:42 ` Wei Liu
2025-02-24 18:39 ` Krzysztof Wilczyński
2025-02-20 15:07 ` Krzysztof Wilczyński
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=20250210175258.pwaqr3dqxstcjmui@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=AND@thinkpad \
--cc=BRIDGE@thinkpad \
--cc=CORE@thinkpad \
--cc=DRIVERS@thinkpad \
--cc=ENDPOINT@thinkpad \
--cc=HOST@thinkpad \
--cc=Hyper-V/Azure@thinkpad \
--cc=NATIVE@thinkpad \
--cc=PCI@thinkpad \
--cc=SUBSYSTEM@thinkpad \
--cc=Supported@thinkpad \
--cc=bhelgaas@google.com \
--cc=decui@microsoft.com \
--cc=eahariha@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=wei.liu@kernel.org \
/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