[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220919170253.GA1011825@bhelgaas>
Date: Mon, 19 Sep 2022 12:02:53 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Frank Li <Frank.Li@....com>
Cc: maz@...nel.org, tglx@...utronix.de, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, shawnguo@...nel.org,
s.hauer@...gutronix.de, kw@...ux.com, bhelgaas@...gle.com,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org,
peng.fan@....com, aisheng.dong@....com, jdmason@...zu.us,
kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
kishon@...com, lorenzo.pieralisi@....com, ntb@...ts.linux.dev,
lznuaa@...il.com, imx@...ts.linux.dev,
manivannan.sadhasivam@...aro.org
Subject: Re: [PATCH v11 5/6] PCI: endpoint: cleanup pci-epf-vntb.c
In subject (I mentioned this last time, too):
PCI: endpoint: pci-epf-vntb: Clean up
On Mon, Sep 19, 2022 at 10:40:37AM -0500, Frank Li wrote:
> Remove unused field: epf_db_phy.
> Remove __iomem before epf_db.
> Change epf_db to u32* from void *
> Remove dupicate check if (readl(ntb->epf_db + i * 4)).
s/dupicate/duplicate/
> Using sizeof(u32) instead of number 4 at all place.
>
> Clean up sparse build warning
> Using epf_db[i] instead of readl() because epf_db is located in local memory
> and allocated by dma_alloc_coherent()
Is "Using epf_db[i] ..." an sparse warning? The indentation suggests
that it is, but it doesn't seem related.
> Replace pci_epc_mem_free_addr() with pci_epf_free_space() at error handle path
> to match pci_epf_alloc_space().
>
> Cleanup warning found by scripts/kernel-doc
> Fix indentation of the struct epf_ntb_ctrl
> Consildate term
s/Consildate/Consolidate/
> host, host1 to HOST
> vhost, vHost, Vhost, VHOST2 to VHOST
Powered by blists - more mailing lists