All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Pei Xiao <xiaopei01@kylinos.cn>
Cc: Hans de Goede <hdegoede@redhat.com>,
	vadimp@nvidia.com,  platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	 davthompson@nvidia.com, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] platform/mellanox: mlxbf-pmc: incorrect type in assignment
Date: Mon, 2 Dec 2024 19:16:06 +0200 (EET)	[thread overview]
Message-ID: <364568ce-140a-85f5-4bf4-1cc641175015@linux.intel.com> (raw)
In-Reply-To: <fece26ad40620b1e0beb733b9bba3de3ce325761.1732088929.git.xiaopei01@kylinos.cn>

On Wed, 20 Nov 2024, Pei Xiao wrote:

> sparse warning,expected 'void __iomem *addr',but got 'void *addr'

Hi,

Thanks for the patch. I've applied this patch to review-ilpo-next branch 
but I had to reformat the commit message. Please make sure you use proper 
spacing and put warnings like that on their own lines in future.

-- 
 i.

> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202411121935.cgFcEMO4-lkp@intel.com/
> Fixes: 423c3361855c ("platform/mellanox: mlxbf-pmc: Add support for BlueField-3")
> Signed-off-by: Pei Xiao <xiaopei01@kylinos.cn>
> ---
>  drivers/platform/mellanox/mlxbf-pmc.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/platform/mellanox/mlxbf-pmc.c b/drivers/platform/mellanox/mlxbf-pmc.c
> index 9d18dfca6a67..9ff7b487dc48 100644
> --- a/drivers/platform/mellanox/mlxbf-pmc.c
> +++ b/drivers/platform/mellanox/mlxbf-pmc.c
> @@ -1168,7 +1168,7 @@ static int mlxbf_pmc_program_l3_counter(unsigned int blk_num, u32 cnt_num, u32 e
>  /* Method to handle crspace counter programming */
>  static int mlxbf_pmc_program_crspace_counter(unsigned int blk_num, u32 cnt_num, u32 evt)
>  {
> -	void *addr;
> +	void __iomem *addr;
>  	u32 word;
>  	int ret;
>  
> @@ -1192,7 +1192,7 @@ static int mlxbf_pmc_program_crspace_counter(unsigned int blk_num, u32 cnt_num,
>  /* Method to clear crspace counter value */
>  static int mlxbf_pmc_clear_crspace_counter(unsigned int blk_num, u32 cnt_num)
>  {
> -	void *addr;
> +	void __iomem *addr;
>  
>  	addr = pmc->block[blk_num].mmio_base +
>  		MLXBF_PMC_CRSPACE_PERFMON_VAL0(pmc->block[blk_num].counters) +
> @@ -1405,7 +1405,7 @@ static int mlxbf_pmc_read_l3_event(unsigned int blk_num, u32 cnt_num, u64 *resul
>  static int mlxbf_pmc_read_crspace_event(unsigned int blk_num, u32 cnt_num, u64 *result)
>  {
>  	u32 word, evt;
> -	void *addr;
> +	void __iomem *addr;
>  	int ret;
>  
>  	addr = pmc->block[blk_num].mmio_base +
> 

      parent reply	other threads:[~2024-12-02 17:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 11:11 drivers/platform/mellanox/mlxbf-pmc.c:1172:14: sparse: sparse: incorrect type in assignment (different address spaces) kernel test robot
2024-11-20  7:51 ` [PATCH] platform/mellanox: mlxbf-pmc: incorrect type in assignment Pei Xiao
2024-11-21 21:09   ` David Thompson
2024-12-02 17:16   ` Ilpo Järvinen [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=364568ce-140a-85f5-4bf4-1cc641175015@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=davthompson@nvidia.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=vadimp@nvidia.com \
    --cc=xiaopei01@kylinos.cn \
    /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.