From: Andrew Donnellan <ajd@linux.ibm.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
bhelgaas@google.com, fbarrat@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, christophe.leroy@csgroup.eu, arnd@arndb.de,
gregkh@linuxfoundation.org, ben.widawsky@intel.com
Cc: jonathan.cameron@huawei.com, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, yangyingliang@huawei.com
Subject: Re: [PATCH 2/2] ocxl: use pci_find_next_dvsec_capability() to simplify the code
Date: Mon, 07 Aug 2023 14:54:15 +1000 [thread overview]
Message-ID: <b521f1165104d67e08d016f96a9e3579489ee9f4.camel@linux.ibm.com> (raw)
In-Reply-To: <20230807031846.77348-3-wangxiongfeng2@huawei.com>
On Mon, 2023-08-07 at 11:18 +0800, Xiongfeng Wang wrote:
> PCI core add pci_find_next_dvsec_capability() to query the next
> DVSEC.
> We can use that core API to simplify the code. Also remove the unused
> macros.
>
> Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Donnellan <ajd@linux.ibm.com>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>,
bhelgaas@google.com, fbarrat@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, christophe.leroy@csgroup.eu, arnd@arndb.de,
gregkh@linuxfoundation.org, ben.widawsky@intel.com
Cc: linux-pci@vger.kernel.org, yangyingliang@huawei.com,
linuxppc-dev@lists.ozlabs.org, jonathan.cameron@huawei.com
Subject: Re: [PATCH 2/2] ocxl: use pci_find_next_dvsec_capability() to simplify the code
Date: Mon, 07 Aug 2023 14:54:15 +1000 [thread overview]
Message-ID: <b521f1165104d67e08d016f96a9e3579489ee9f4.camel@linux.ibm.com> (raw)
In-Reply-To: <20230807031846.77348-3-wangxiongfeng2@huawei.com>
On Mon, 2023-08-07 at 11:18 +0800, Xiongfeng Wang wrote:
> PCI core add pci_find_next_dvsec_capability() to query the next
> DVSEC.
> We can use that core API to simplify the code. Also remove the unused
> macros.
>
> Signed-off-by: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com>
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2023-08-07 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` 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 [this message]
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=b521f1165104d67e08d016f96a9e3579489ee9f4.camel@linux.ibm.com \
--to=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=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 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.