From: Wei Xu <xuwei5@hisilicon.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: <linux-kernel@vger.kernel.org>, <soc@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Jonathan.Cameron@Huawei.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH v2 0/2] soc: hisilicon: kunpeng_hccs: add dependency and enhance verification
Date: Thu, 25 Apr 2024 19:16:15 +0800 [thread overview]
Message-ID: <662A3B7F.4060003@hisilicon.com> (raw)
In-Reply-To: <20240417094801.25393-1-lihuisong@huawei.com>
Hi Huisong,
On 2024/4/17 17:47, Huisong Li wrote:
> Add PCC dependency and enhance verification during the probe phase.
>
> ---
> v2: fix the log on failure.
>
> Huisong Li (2):
> soc: hisilicon: kunpeng_hccs: Add the check for obtaining complete
> port attribute
> soc: hisilicon: kunpeng_hccs: replace MAILBOX dependency with PCC
>
> drivers/soc/hisilicon/Kconfig | 2 +-
> drivers/soc/hisilicon/kunpeng_hccs.c | 6 ++++++
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
Thanks!
Series applied to the HiSilicon driver tree with minor changes in the commit msg:
https://github.com/hisilicon/linux-hisi/tree/next/drivers
Best Regards,
Wei
prev parent reply other threads:[~2024-04-25 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 8:19 [PATCH 0/2] soc: hisilicon: kunpeng_hccs: add dependency and enhance verification Huisong Li
2024-04-03 8:19 ` [PATCH 1/2] soc: hisilicon: kunpeng_hccs: Add the check for obtaining complete port attribute Huisong Li
2024-04-15 1:17 ` Wei Xu
2024-04-16 1:17 ` lihuisong (C)
2024-04-03 8:19 ` [PATCH 2/2] soc: hisilicon: kunpeng_hccs: replace MAILBOX dependency with PCC Huisong Li
2024-04-17 9:47 ` [PATCH v2 0/2] soc: hisilicon: kunpeng_hccs: add dependency and enhance verification Huisong Li
2024-04-17 9:48 ` [PATCH v2 1/2] soc: hisilicon: kunpeng_hccs: Add the check for obtaining complete port attribute Huisong Li
2024-04-17 9:48 ` [PATCH v2 2/2] soc: hisilicon: kunpeng_hccs: replace MAILBOX dependency with PCC Huisong Li
2024-04-25 11:16 ` Wei Xu [this message]
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=662A3B7F.4060003@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=soc@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).