From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Fan Gong <gongfan1@huawei.com>, Zhu Yikai <zhuyikai1@h-partners.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Bjorn Helgaas <helgaas@kernel.org>, luosifu <luosifu@huawei.com>,
Xin Guo <guoxin09@huawei.com>,
Shen Chenyang <shenchenyang1@hisilicon.com>,
Zhou Shuai <zhoushuai28@huawei.com>, Wu Like <wulike1@huawei.com>,
Shi Jing <shijing34@huawei.com>,
Luo Yang <luoyang82@h-partners.com>,
Meny Yossefi <meny.yossefi@huawei.com>,
Gur Stavi <gur.stavi@huawei.com>, Lee Trager <lee@trager.us>,
Michael Ellerman <mpe@ellerman.id.au>,
Suman Ghosh <sumang@marvell.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: Re: [PATCH net-next v04 06/14] hinic3: Nic_io initialization
Date: Sun, 7 Sep 2025 18:02:11 +0100 [thread overview]
Message-ID: <98c93693-0647-4c7e-ac1c-729502beab76@linux.dev> (raw)
In-Reply-To: <0d48674ae76a54bf52dcdba64fb60eb26e7e7e70.1757057860.git.zhuyikai1@h-partners.com>
On 05/09/2025 09:28, Fan Gong wrote:
> Add nic_io initialization to enable NIC service, initialize function table
> and negotiate activation of NIC features.
[...]
> +static DEFINE_IDA(hinic3_adev_ida);
> +
> +static int hinic3_adev_idx_alloc(void)
> +{
> + return ida_alloc(&hinic3_adev_ida, GFP_KERNEL);
> +}
> +
> +static void hinic3_adev_idx_free(int id)
> +{
> + ida_free(&hinic3_adev_ida, id);
> +}
> +
> int hinic3_init_hwdev(struct pci_dev *pdev)
> {
> struct hinic3_pcidev *pci_adapter = pci_get_drvdata(pdev);
> @@ -451,6 +463,7 @@ int hinic3_init_hwdev(struct pci_dev *pdev)
> hwdev->pdev = pci_adapter->pdev;
> hwdev->dev = &pci_adapter->pdev->dev;
> hwdev->func_state = 0;
> + hwdev->dev_id = hinic3_adev_idx_alloc();
Why do you need dev_id? It's not used anywhere in the patchset. The
commit doesn't explain it neither...
next prev parent reply other threads:[~2025-09-07 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 8:28 [PATCH net-next v04 00/14] net: hinic3: Add a driver for Huawei 3rd gen NIC - sw and hw initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 01/14] hinic3: HW initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 02/14] hinic3: HW management interfaces Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 03/14] hinic3: HW common function initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 04/14] hinic3: HW capability initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 05/14] hinic3: Command Queue flush interfaces Fan Gong
2025-09-07 16:55 ` Vadim Fedorenko
2025-09-05 8:28 ` [PATCH net-next v04 06/14] hinic3: Nic_io initialization Fan Gong
2025-09-07 17:02 ` Vadim Fedorenko [this message]
2025-09-08 3:27 ` Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 07/14] hinic3: Queue pair endianness improvements Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 08/14] hinic3: Queue pair resource initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 09/14] hinic3: Queue pair context initialization Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 10/14] hinic3: Tx & Rx configuration Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 11/14] hinic3: Add Rss function Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 12/14] hinic3: Add port management Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 13/14] hinic3: Fix missing napi->dev in netif_queue_set_napi Fan Gong
2025-09-05 8:28 ` [PATCH net-next v04 14/14] hinic3: Fix code style (Missing a blank line before return) Fan Gong
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=98c93693-0647-4c7e-ac1c-729502beab76@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=christophe.jaillet@wanadoo.fr \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gongfan1@huawei.com \
--cc=guoxin09@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=helgaas@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luosifu@huawei.com \
--cc=luoyang82@h-partners.com \
--cc=meny.yossefi@huawei.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=shenchenyang1@hisilicon.com \
--cc=shijing34@huawei.com \
--cc=sumang@marvell.com \
--cc=wulike1@huawei.com \
--cc=zhoushuai28@huawei.com \
--cc=zhuyikai1@h-partners.com \
/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).