From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <bhelgaas@google.com>, <fbarrat@linux.ibm.com>,
<ajd@linux.ibm.com>, <mpe@ellerman.id.au>, <npiggin@gmail.com>,
<christophe.leroy@csgroup.eu>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>, <ben.widawsky@intel.com>,
<wangxiongfeng2@huawei.com>
Cc: <jonathan.cameron@huawei.com>, <linux-pci@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>, <yangyingliang@huawei.com>
Subject: [PATCH 0/2] introduce pci_find_next_dvsec_capability() to simplify the code
Date: Mon, 7 Aug 2023 11:18:44 +0800 [thread overview]
Message-ID: <20230807031846.77348-1-wangxiongfeng2@huawei.com> (raw)
Some devices may have several DVSEC(Designated Vendor-Specific Extended
Capability) entries with the same DVSEC ID. Introduce
pci_find_next_dvsec_capability() to simplify the code.
Xiongfeng Wang (2):
PCI: Add pci_find_next_dvsec_capability to find next designated VSEC
ocxl: use pci_find_next_dvsec_capability() to simplify the code
arch/powerpc/platforms/powernv/ocxl.c | 20 ++-------------
drivers/misc/ocxl/config.c | 21 +++++----------
drivers/pci/pci.c | 37 ++++++++++++++++++---------
include/linux/pci.h | 2 ++
include/misc/ocxl-config.h | 4 ---
5 files changed, 35 insertions(+), 49 deletions(-)
--
2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
To: <bhelgaas@google.com>, <fbarrat@linux.ibm.com>,
<ajd@linux.ibm.com>, <mpe@ellerman.id.au>, <npiggin@gmail.com>,
<christophe.leroy@csgroup.eu>, <arnd@arndb.de>,
<gregkh@linuxfoundation.org>, <ben.widawsky@intel.com>,
<wangxiongfeng2@huawei.com>
Cc: linux-pci@vger.kernel.org, yangyingliang@huawei.com,
linuxppc-dev@lists.ozlabs.org, jonathan.cameron@huawei.com
Subject: [PATCH 0/2] introduce pci_find_next_dvsec_capability() to simplify the code
Date: Mon, 7 Aug 2023 11:18:44 +0800 [thread overview]
Message-ID: <20230807031846.77348-1-wangxiongfeng2@huawei.com> (raw)
Some devices may have several DVSEC(Designated Vendor-Specific Extended
Capability) entries with the same DVSEC ID. Introduce
pci_find_next_dvsec_capability() to simplify the code.
Xiongfeng Wang (2):
PCI: Add pci_find_next_dvsec_capability to find next designated VSEC
ocxl: use pci_find_next_dvsec_capability() to simplify the code
arch/powerpc/platforms/powernv/ocxl.c | 20 ++-------------
drivers/misc/ocxl/config.c | 21 +++++----------
drivers/pci/pci.c | 37 ++++++++++++++++++---------
include/linux/pci.h | 2 ++
include/misc/ocxl-config.h | 4 ---
5 files changed, 35 insertions(+), 49 deletions(-)
--
2.20.1
next reply other threads:[~2023-08-07 3:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 3:18 Xiongfeng Wang [this message]
2023-08-07 3:18 ` [PATCH 0/2] introduce pci_find_next_dvsec_capability() to simplify the code Xiongfeng Wang
2023-08-07 3:18 ` [PATCH 1/2] PCI: Add pci_find_next_dvsec_capability to find next designated VSEC Xiongfeng Wang
2023-08-07 3:18 ` Xiongfeng Wang
2023-08-07 4:24 ` Andrew Donnellan
2023-08-07 4:24 ` Andrew Donnellan
2023-08-07 20:33 ` Bjorn Helgaas
2023-08-07 20:33 ` Bjorn Helgaas
2023-08-07 3:18 ` [PATCH 2/2] ocxl: use pci_find_next_dvsec_capability() to simplify the code Xiongfeng Wang
2023-08-07 3:18 ` Xiongfeng Wang
2023-08-07 4:54 ` Andrew Donnellan
2023-08-07 4:54 ` Andrew Donnellan
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=20230807031846.77348-1-wangxiongfeng2@huawei.com \
--to=wangxiongfeng2@huawei.com \
--cc=ajd@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=ben.widawsky@intel.com \
--cc=bhelgaas@google.com \
--cc=christophe.leroy@csgroup.eu \
--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=mpe@ellerman.id.au \
--cc=npiggin@gmail.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 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.