linux-kernel - RE: [PATCH v2] PCI: hv: Correct a comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <SN6PR02MB41570947C2A84614FAFCF8EED4F02@SN6PR02MB4157.namprd02.prod.outlook.com>
Date: Sat, 8 Feb 2025 15:45:28 +0000
From: Michael Kelley <mhklinux@...look.com>
To: Easwar Hariharan <eahariha@...ux.microsoft.com>, "K. Y. Srinivasan"
	<kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>, Wei Liu
	<wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>, Lorenzo Pieralisi
	<lpieralisi@...nel.org>, Krzysztof Wilczyński
	<kw@...ux.com>, Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>, Rob
 Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>, "open
 list:Hyper-V/Azure CORE AND DRIVERS" <linux-hyperv@...r.kernel.org>, "open
 list:PCI NATIVE HOST BRIDGE AND ENDPOINT DRIVERS"
	<linux-pci@...r.kernel.org>, open list <linux-kernel@...r.kernel.org>,
	"Hyper-V/Azure@....codeaurora.org" <Hyper-V/Azure@....codeaurora.org>,
	"CORE@....codeaurora.org" <CORE@....codeaurora.org>, "AND@....codeaurora.org"
	<AND@....codeaurora.org>, "DRIVERS@....codeaurora.org"
	<DRIVERS@....codeaurora.org>, "\"status:Supported\"@web.codeaurora.org"
	<"status:Supported"@web.codeaurora.org>, "PCI@....codeaurora.org"
	<PCI@....codeaurora.org>, "NATIVE@....codeaurora.org"
	<NATIVE@....codeaurora.org>, "HOST@....codeaurora.org"
	<HOST@....codeaurora.org>, "BRIDGE@....codeaurora.org"
	<BRIDGE@....codeaurora.org>, "ENDPOINT@....codeaurora.org"
	<ENDPOINT@....codeaurora.org>, "SUBSYSTEM@....codeaurora.org"
	<SUBSYSTEM@....codeaurora.org>
Subject: RE: [PATCH v2] PCI: hv: Correct a comment

From: Easwar Hariharan <eahariha@...ux.microsoft.com> Sent: Friday, February 7, 2025 11:07 AM
> 
> 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@...ux.microsoft.com>
> ---
>  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
> 

Reviewed-by: Michael Kelley <mhklinux@...look.com>