From: Bjorn Helgaas <helgaas@kernel.org>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: ben.widawsky@intel.com, ajd@linux.ibm.com, arnd@arndb.de,
jonathan.cameron@huawei.com, yangyingliang@huawei.com,
linux-pci@vger.kernel.org, fbarrat@linux.ibm.com,
npiggin@gmail.com, david.e.box@linux.intel.com,
gregkh@linuxfoundation.org, bhelgaas@google.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 1/2] PCI: Add pci_find_next_dvsec_capability to find next Designated VSEC
Date: Tue, 8 Aug 2023 10:58:14 -0500 [thread overview]
Message-ID: <20230808155814.GA313884@bhelgaas> (raw)
In-Reply-To: <20230808040858.183568-2-wangxiongfeng2@huawei.com>
Don't re-post just for this, but if you do repost, add "()" after the
function name in the subject line, as you did for the 2/2 patch.
On Tue, Aug 08, 2023 at 12:08:57PM +0800, Xiongfeng Wang wrote:
> Some devices may have several DVSEC (Designated Vendor-Specific Extended
> Capability) entries with the same DVSEC ID. Add
> pci_find_next_dvsec_capability() to find them all.
next prev parent reply other threads:[~2023-08-08 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 4:08 [PATCH v2 0/2] Introduce pci_find_next_dvsec_capability() to simplify the code Xiongfeng Wang
2023-08-08 4:08 ` [PATCH v2 1/2] PCI: Add pci_find_next_dvsec_capability to find next Designated VSEC Xiongfeng Wang
2023-08-08 15:58 ` Bjorn Helgaas [this message]
2023-08-08 4:08 ` [PATCH v2 2/2] ocxl: use pci_find_next_dvsec_capability() to simplify the code Xiongfeng Wang
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=20230808155814.GA313884@bhelgaas \
--to=helgaas@kernel.org \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=ben.widawsky@intel.com \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=fbarrat@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyingliang@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 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).