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>, <arnd@arndb.de>, <krzk@kernel.org>,
<sudeep.holla@arm.com>, <liuyonglong@huawei.com>,
<xuwei5@hisilicon.com>
Subject: Re: [PATCH v3 0/5] soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and interrupt ack
Date: Fri, 8 Dec 2023 15:18:34 +0800 [thread overview]
Message-ID: <6572C34A.7010101@hisilicon.com> (raw)
In-Reply-To: <20231201034534.7276-1-lihuisong@huawei.com>
Hi Huisong,
On 2023/12/1 11:45, Huisong Li wrote:
> The main purpose of this series is to support the platform with PCC type3
> and interrupt ack. At the same time, this series also fix some clean codes
> and modify the incorrect email domain name.
>
> ---
> v3:
> - remove inline tag of two wait_cmd_complete function.
> - delete variable 'ret' in hccs_wait_cmd_complete_by_irq()
> - add a new patch which fix incorrect email domain name in document.
>
> v2:
> - using a version specific structure to replace device version according
> to Jonathan's advice.
> - add a new patch that remove an unused blank line.
>
> Huisong Li (5):
> soc: hisilicon: kunpeng_hccs: Fix some incorrect format strings
> soc: hisilicon: kunpeng_hccs: Add failure log for no _CRS method
> soc: hisilicon: kunpeng_hccs: Remove an unused blank line
> doc: kunpeng_hccs: Fix incorrect email domain name
> soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and
> interrupt ack
>
> .../sysfs-devices-platform-kunpeng_hccs | 6 +-
> drivers/soc/hisilicon/kunpeng_hccs.c | 152 ++++++++++++++----
> drivers/soc/hisilicon/kunpeng_hccs.h | 15 ++
> 3 files changed, 137 insertions(+), 36 deletions(-)
>
Thanks!
Series applied to the HiSilicon driver tree.
Best Regards,
Wei
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-12-08 7:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 5:45 [PATCH v1 0/3] soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and interrupt ack Huisong Li
2023-11-09 5:45 ` [PATCH v1 1/3] soc: hisilicon: kunpeng_hccs: Fix some incorrect format strings Huisong Li
2023-11-28 15:25 ` Jonathan Cameron
2023-11-09 5:45 ` [PATCH v1 2/3] soc: hisilicon: kunpeng_hccs: Add failure log for no _CRS method Huisong Li
2023-11-28 15:22 ` Jonathan Cameron
2023-11-09 5:45 ` [PATCH v1 3/3] soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and interrupt ack Huisong Li
2023-11-28 15:44 ` Jonathan Cameron
2023-11-30 1:16 ` lihuisong (C)
2023-11-30 13:45 ` [PATCH v2 0/4] " Huisong Li
2023-11-30 13:45 ` [PATCH v2 1/4] soc: hisilicon: kunpeng_hccs: Fix some incorrect format strings Huisong Li
2023-11-30 13:45 ` [PATCH v2 2/4] soc: hisilicon: kunpeng_hccs: Add failure log for no _CRS method Huisong Li
2023-11-30 13:45 ` [PATCH v2 3/4] soc: hisilicon: kunpeng_hccs: remove an unused blank line Huisong Li
2023-11-30 14:42 ` Jonathan Cameron
2023-11-30 13:45 ` [PATCH v2 4/4] soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and interrupt ack Huisong Li
2023-11-30 14:49 ` Jonathan Cameron
2023-12-01 2:45 ` lihuisong (C)
2023-12-01 3:45 ` [PATCH v3 0/5] " Huisong Li
2023-12-01 3:45 ` [PATCH v3 1/5] soc: hisilicon: kunpeng_hccs: Fix some incorrect format strings Huisong Li
2023-12-01 3:45 ` [PATCH v3 2/5] soc: hisilicon: kunpeng_hccs: Add failure log for no _CRS method Huisong Li
2023-12-01 3:45 ` [PATCH v3 3/5] soc: hisilicon: kunpeng_hccs: Remove an unused blank line Huisong Li
2023-12-01 3:45 ` [PATCH v3 4/5] doc: kunpeng_hccs: Fix incorrect email domain name Huisong Li
2023-12-01 3:45 ` [PATCH v3 5/5] soc: hisilicon: kunpeng_hccs: Support the platform with PCC type3 and interrupt ack Huisong Li
2023-12-08 7:18 ` 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=6572C34A.7010101@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--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 \
--cc=sudeep.holla@arm.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).