From: patchwork-bot+linux-soc@kernel.org
To: lihuisong (C) <lihuisong@huawei.com>
Cc: soc@kernel.org
Subject: Re: [PATCH v2] soc: kunpeng_hccs: fix some sparse warnings about incorrect type
Date: Tue, 22 Aug 2023 02:31:16 +0000 [thread overview]
Message-ID: <169267147638.32531.13517831572097065300.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230816073706.33297-1-lihuisong@huawei.com>
Hello:
This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Wed, 16 Aug 2023 15:37:06 +0800 you wrote:
> This patch fixes some sparse warnings about incorrect type.
> The address about PCC communication space should use '__iomem' tag.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202308151142.dH5Muhva-lkp@intel.com/
> Fixes: 886bdf9c883b ("soc: hisilicon: Support HCCS driver on Kunpeng SoC")
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
>
> [...]
Here is the summary with links:
- [v2] soc: kunpeng_hccs: fix some sparse warnings about incorrect type
https://git.kernel.org/soc/soc/c/7d6612834d17
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-08-22 2:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 12:52 [PATCH] soc: kunpeng_hccs: fix some sparse warnings about incorrect type Huisong Li
2023-08-15 12:52 ` Huisong Li
2023-08-16 5:35 ` kernel test robot
2023-08-16 7:37 ` [PATCH v2] " Huisong Li
2023-08-16 7:37 ` Huisong Li
2023-08-22 2:31 ` patchwork-bot+linux-soc [this message]
2023-08-16 13:17 ` [PATCH] " Arnd Bergmann
2023-08-16 13:17 ` Arnd Bergmann
2023-08-17 1:37 ` lihuisong (C)
2023-08-17 1:37 ` lihuisong (C)
2023-08-17 11:54 ` Arnd Bergmann
2023-08-17 11:54 ` Arnd Bergmann
2023-08-18 1:38 ` lihuisong (C)
2023-08-18 1:38 ` lihuisong (C)
2023-08-18 1:57 ` Arnd Bergmann
2023-08-18 1:57 ` Arnd Bergmann
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=169267147638.32531.13517831572097065300.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=lihuisong@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 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.