netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Yanteng Si <siyanteng@loongson.cn>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, peppe.cavallaro@st.com,
	alexandre.torgue@foss.st.com, joabreu@synopsys.com,
	fancer.lancer@gmail.com, Jose.Abreu@synopsys.com,
	chenhuacai@kernel.org, linux@armlinux.org.uk,
	guyinggang@loongson.cn, netdev@vger.kernel.org,
	chris.chenfeiyang@gmail.com, siyanteng01@gmail.com
Subject: Re: [PATCH net-next v11 3/6] net: stmmac: dwmac-loongson: Use PCI_DEVICE_DATA() macro for device identification
Date: Fri, 12 Apr 2024 18:49:39 -0700	[thread overview]
Message-ID: <20240412184939.2b022d42@kernel.org> (raw)
In-Reply-To: <b078687371ec7e740e3a630aedd3e76ecfdc1078.1712917541.git.siyanteng@loongson.cn>

On Fri, 12 Apr 2024 19:28:08 +0800 Yanteng Si wrote:
> Just use PCI_DEVICE_DATA() macro for device identification,
> No changes to function functionality.
> 
> Signed-off-by: Feiyang Chen <chenfeiyang@loongson.cn>
> Signed-off-by: Yinggang Gu <guyinggang@loongson.cn>
> Signed-off-by: Yanteng Si <siyanteng@loongson.cn>
> ---
>  drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c b/drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c
> index 9e40c28d453a..995c9bd144e0 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c
> @@ -213,7 +213,7 @@ static SIMPLE_DEV_PM_OPS(loongson_dwmac_pm_ops, loongson_dwmac_suspend,
>  			 loongson_dwmac_resume);
>  
>  static const struct pci_device_id loongson_dwmac_id_table[] = {
> -	{ PCI_VDEVICE(LOONGSON, 0x7a03) },
> +	{ PCI_DEVICE_DATA(LOONGSON, GMAC, &loongson_gmac_pci_info) },
>  	{}
>  };
>  MODULE_DEVICE_TABLE(pci, loongson_dwmac_id_table);

In file included from ../drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c:6:
../include/linux/pci.h:1061:51: error: ‘PCI_DEVICE_ID_LOONGSON_GMAC’ undeclared here (not in a function); did you mean ‘PCI_DEVICE_ID_LOONGSON_HDA’?
 1061 |         .vendor = PCI_VENDOR_ID_##vend, .device = PCI_DEVICE_ID_##vend##_##dev, \
      |                                                   ^~~~~~~~~~~~~~
../drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c:216:11: note: in expansion of macro ‘PCI_DEVICE_DATA’
  216 |         { PCI_DEVICE_DATA(LOONGSON, GMAC, &loongson_gmac_pci_info) },
      |           ^~~~~~~~~~~~~~~
../drivers/net/ethernet/stmicro/stmmac/dwmac-loongson.c:216:44: error: ‘loongson_gmac_pci_info’ undeclared here (not in a function)
  216 |         { PCI_DEVICE_DATA(LOONGSON, GMAC, &loongson_gmac_pci_info) },
      |                                            ^~~~~~~~~~~~~~~~~~~~~~
../include/linux/pci.h:1063:41: note: in definition of macro ‘PCI_DEVICE_DATA’
 1063 |         .driver_data = (kernel_ulong_t)(data)
      |                                         ^~~~
-- 
pw-bot: cr

  reply	other threads:[~2024-04-13  1:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 11:28 [PATCH net-next v11 0/6] stmmac: Add Loongson platform support Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 1/6] net: stmmac: Move all PHYLINK MAC capabilities initializations to MAC-specific setup methods Yanteng Si
2024-04-12 18:32   ` Serge Semin
2024-04-18  5:02     ` Yanteng Si
2024-04-18  9:53       ` Serge Semin
2024-04-19  7:01         ` Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 2/6] net: stmmac: Add multi-channel support Yanteng Si
2024-04-18 11:02   ` Serge Semin
2024-04-19  9:02     ` Yanteng Si
2024-04-19  9:17       ` Serge Semin
2024-04-19  9:51         ` Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 3/6] net: stmmac: dwmac-loongson: Use PCI_DEVICE_DATA() macro for device identification Yanteng Si
2024-04-13  1:49   ` Jakub Kicinski [this message]
2024-04-15  2:21     ` Yanteng Si
2024-04-18 11:14       ` Serge Semin
2024-04-18 12:31         ` Serge Semin
2024-04-19  9:40           ` Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 4/6] net: stmmac: dwmac-loongson: Introduce GMAC setup Yanteng Si
2024-04-18 12:26   ` Serge Semin
2024-04-19 10:06     ` Yanteng Si
2024-04-22 10:17   ` Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 5/6] net: stmmac: dwmac-loongson: Add full PCI support Yanteng Si
2024-04-18 13:08   ` Serge Semin
2024-04-20  2:41     ` Yanteng Si
2024-04-12 11:28 ` [PATCH net-next v11 6/6] net: stmmac: dwmac-loongson: Add Loongson GNET support Yanteng Si
2024-04-18 14:01   ` Serge Semin
2024-04-20 11:02     ` Yanteng Si
2024-04-21  5:35       ` Yanteng Si
2024-04-23 13:16     ` Yanteng Si
2024-04-24 14:11     ` Huacai Chen
2024-04-24 14:46       ` Russell King (Oracle)
2024-04-25  8:07       ` Yanteng Si
2024-04-24 13:37   ` Huacai Chen
2024-04-25  8:09     ` Yanteng Si
2024-04-12 18:34 ` [PATCH net-next v11 0/6] stmmac: Add Loongson platform support Serge Semin
2024-04-18  5:16   ` Yanteng Si

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=20240412184939.2b022d42@kernel.org \
    --to=kuba@kernel.org \
    --cc=Jose.Abreu@synopsys.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=chenhuacai@kernel.org \
    --cc=chris.chenfeiyang@gmail.com \
    --cc=fancer.lancer@gmail.com \
    --cc=guyinggang@loongson.cn \
    --cc=hkallweit1@gmail.com \
    --cc=joabreu@synopsys.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    /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).