From: Dan Carpenter <dan.carpenter@linaro.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Joao Pinto" <jpinto@synopsys.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Wei Yongjun" <weiyongjun1@huawei.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Zijun Hu" <quic_zijuhu@quicinc.com>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org,
"Harshit Mogalapalli" <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH v3 0/3] PCI: endpoint: fix bug for 2 APIs and simplify 1 API
Date: Thu, 12 Dec 2024 12:35:07 +0300 [thread overview]
Message-ID: <1fac71d8-dcfe-4924-ab01-dc85a822b740@stanley.mountain> (raw)
In-Reply-To: <20241210-pci-epc-core_fix-v3-0-4d86dd573e4b@quicinc.com>
On Tue, Dec 10, 2024 at 10:00:17PM +0800, Zijun Hu wrote:
> This patch series is to fix bug for APIs
> - devm_pci_epc_destroy().
> - pci_epf_remove_vepf().
>
> and simplify APIs below:
> - pci_epc_get().
>
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
This is very good. This is Config FS. Is there a kself test for configfs
or did you create your own test?
regards,
dan carpenter
next prev parent reply other threads:[~2024-12-12 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 14:00 [PATCH v3 0/3] PCI: endpoint: fix bug for 2 APIs and simplify 1 API Zijun Hu
2024-12-10 14:00 ` [PATCH v3 1/3] PCI: endpoint: Fix that API devm_pci_epc_destroy() fails to destroy the EPC device Zijun Hu
2024-12-10 14:00 ` [PATCH v3 2/3] PCI: endpoint: Simplify API pci_epc_get() implementation Zijun Hu
2024-12-12 18:00 ` Frank Li
2024-12-10 14:00 ` [PATCH v3 3/3] PCI: endpoint: Fix API pci_epf_add_vepf() returning -EBUSY error Zijun Hu
2024-12-12 18:03 ` Frank Li
2024-12-12 9:35 ` Dan Carpenter [this message]
2024-12-12 11:56 ` [PATCH v3 0/3] PCI: endpoint: fix bug for 2 APIs and simplify 1 API Zijun Hu
2024-12-12 19:12 ` Bjorn Helgaas
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=1fac71d8-dcfe-4924-ab01-dc85a822b740@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=bhelgaas@google.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jpinto@synopsys.com \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_zijuhu@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=weiyongjun1@huawei.com \
--cc=zijun_hu@icloud.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