From: Jiri Pirko <jiri@resnulli.us>
To: han.junyang@zte.com.cn
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
ran.ming@zte.com.cn, han.chengfei@zte.com.cn,
zhang.yanze@zte.com.cn
Subject: Re: [PATCH net-next v8 2/2] dinghai: add hardware register access and PCI? capability scanning
Date: Tue, 14 Jul 2026 15:10:37 +0200 [thread overview]
Message-ID: <alY0foKtgceGUCtP@FV6GYCPJ69> (raw)
In-Reply-To: <20260713222804514zLeRvL3Su1xlklpOdahhF@zte.com.cn>
Mon, Jul 13, 2026 at 04:28:04PM +0200, han.junyang@zte.com.cn wrote:
[..]
>@@ -48,5 +85,34 @@ struct zxdh_pf_device {
> void *dh_core_alloc_priv(struct dh_core_dev *dh_dev, size_t size);
> void dh_core_free_priv(struct dh_core_dev *dh_dev);
> void dh_pf_pci_close(struct dh_core_dev *dev);
>+int zxdh_pf_pci_find_capability(struct pci_dev *pdev, u8 cfg_type,
>+ u32 ioresource_types, int *bars);
>+void __iomem *zxdh_pf_map_capability(struct dh_core_dev *dh_dev, int off,
>+ size_t minlen, u32 align,
>+ u32 start, u32 size,
>+ size_t *len, resource_size_t *pa,
>+ u32 *bar_off);
>+int zxdh_pf_common_cfg_init(struct dh_core_dev *dh_dev);
>+int zxdh_pf_notify_cfg_init(struct dh_core_dev *dh_dev);
>+int zxdh_pf_device_cfg_init(struct dh_core_dev *dh_dev);
>+void zxdh_pf_modern_cfg_uninit(struct dh_core_dev *dh_dev);
>+int zxdh_pf_modern_cfg_init(struct dh_core_dev *dh_dev);
>+u16 zxdh_pf_get_queue_notify_off(struct dh_core_dev *dh_dev,
>+ u16 phy_index, u16 index);
>+void __iomem *zxdh_pf_map_vq_notify(struct dh_core_dev *dh_dev,
>+ u16 phy_index, u16 index,
>+ resource_size_t *pa);
>+void zxdh_pf_unmap_vq_notify(struct dh_core_dev *dh_dev, void __iomem *priv);
>+void zxdh_pf_set_status(struct dh_core_dev *dh_dev, u8 status);
>+u8 zxdh_pf_get_status(struct dh_core_dev *dh_dev);
>+u8 zxdh_pf_get_cfg_gen(struct dh_core_dev *dh_dev);
>+void zxdh_pf_get_vf_mac(struct dh_core_dev *dh_dev, u8 *mac, int vf_id);
>+void zxdh_pf_set_vf_mac_reg(struct zxdh_pf_device *pf_dev,
>+ u8 *mac, int vf_id);
>+void zxdh_pf_set_vf_mac(struct dh_core_dev *dh_dev, u8 *mac, int vf_id);
I don't follow. You introduce functions yet you never use them? When you
introduce some function, you need to use it in the same patchset.
Honestly, I would expect quite different patchset quality in V8 :/
>+void zxdh_set_mac(struct dh_core_dev *dh_dev, u8 *mac);
>+void zxdh_get_mac(struct dh_core_dev *dh_dev, u8 *mac);
>+u64 zxdh_pf_get_features(struct dh_core_dev *dh_dev);
>+void zxdh_pf_set_features(struct dh_core_dev *dh_dev, u64 features);
>
> #endif /* __ZXDH_EN_PF_H__ */
>--
>2.27.0
>
prev parent reply other threads:[~2026-07-14 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 14:21 [PATCH net-next v8 0/2] Add ZTE DingHai Ethernet PF driver han.junyang
2026-07-13 14:24 ` [PATCH net-next v8 1/2] dinghai: add ZTE network driver support han.junyang
2026-07-14 13:06 ` Jiri Pirko
2026-07-13 14:28 ` [PATCH net-next v8 2/2] dinghai: add hardware register access and PCI capability scanning han.junyang
2026-07-14 13:10 ` Jiri Pirko [this message]
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=alY0foKtgceGUCtP@FV6GYCPJ69 \
--to=jiri@resnulli.us \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=han.chengfei@zte.com.cn \
--cc=han.junyang@zte.com.cn \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ran.ming@zte.com.cn \
--cc=zhang.yanze@zte.com.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