From: Jason Gunthorpe <jgg@nvidia.com>
To: Junxian Huang <huangjunxian6@hisilicon.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, linuxarm@huawei.com,
tangchengchang@huawei.com
Subject: Re: [PATCH for-next 1/8] RDMA/hns: Add helpers to obtain netdev and bus_num from hr_dev
Date: Wed, 24 Sep 2025 11:00:52 -0300 [thread overview]
Message-ID: <20250924140052.GA2674734@nvidia.com> (raw)
In-Reply-To: <20250913090615.212720-2-huangjunxian6@hisilicon.com>
On Sat, Sep 13, 2025 at 05:06:08PM +0800, Junxian Huang wrote:
> Add helpers to obtain netdev and bus_num from hr_dev.
bus number seems like a strange way to do this? Aren't your PFs a PCI
multi-function-device? Shouldn't it check for same-function instead?
Jason
next prev parent reply other threads:[~2025-09-24 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-13 9:06 [PATCH for-next 0/8] RDMA/hns: Support RoCE bonding Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 1/8] RDMA/hns: Add helpers to obtain netdev and bus_num from hr_dev Junxian Huang
2025-09-24 14:00 ` Jason Gunthorpe [this message]
2025-09-28 10:12 ` Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 2/8] RDMA/hns: Initialize bonding resources Junxian Huang
2025-09-24 14:04 ` Jason Gunthorpe
2025-10-13 8:25 ` Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 3/8] RDMA/hns: Add bonding event handler Junxian Huang
2025-09-24 14:05 ` Jason Gunthorpe
2025-09-13 9:06 ` [PATCH for-next 4/8] RDMA/hns: Add bonding cmds Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 5/8] RDMA/hns: Implement bonding init/uninit process Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 6/8] RDMA/hns: Add delayed work for bonding Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 7/8] RDMA/hns: Support link state reporting for bond Junxian Huang
2025-09-13 9:06 ` [PATCH for-next 8/8] RDMA/hns: Support reset recovery " Junxian Huang
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=20250924140052.GA2674734@nvidia.com \
--to=jgg@nvidia.com \
--cc=huangjunxian6@hisilicon.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=tangchengchang@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.