From: Joerg Roedel <joro@8bytes.org>
To: guoren@kernel.org
Cc: tjeznach@rivosinc.com, will@kernel.org, robin.murphy@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
baolu.lu@linux.intel.com, zong.li@sifive.com,
iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH] iommu/riscv: Fixup compile warning
Date: Fri, 17 Jan 2025 08:58:34 +0100 [thread overview]
Message-ID: <Z4oNqjtzYkjRJlYr@8bytes.org> (raw)
In-Reply-To: <20250103024616.3359159-1-guoren@kernel.org>
On Thu, Jan 02, 2025 at 09:46:16PM -0500, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> When __BITS_PER_LONG == 32, size_t is defined as unsigned int rather
> than unsigned long. Therefore, we should use size_t to avoid
> type-checking errors.
>
> Fixes: 488ffbf18171 ("iommu/riscv: Paging domain support")
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Tomasz Jeznach <tjeznach@rivosinc.com>
> ---
> drivers/iommu/riscv/iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: guoren@kernel.org
Cc: tjeznach@rivosinc.com, will@kernel.org, robin.murphy@arm.com,
paul.walmsley@sifive.com, palmer@dabbelt.com,
baolu.lu@linux.intel.com, zong.li@sifive.com,
iommu@lists.linux.dev, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH] iommu/riscv: Fixup compile warning
Date: Fri, 17 Jan 2025 08:58:34 +0100 [thread overview]
Message-ID: <Z4oNqjtzYkjRJlYr@8bytes.org> (raw)
In-Reply-To: <20250103024616.3359159-1-guoren@kernel.org>
On Thu, Jan 02, 2025 at 09:46:16PM -0500, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> When __BITS_PER_LONG == 32, size_t is defined as unsigned int rather
> than unsigned long. Therefore, we should use size_t to avoid
> type-checking errors.
>
> Fixes: 488ffbf18171 ("iommu/riscv: Paging domain support")
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Tomasz Jeznach <tjeznach@rivosinc.com>
> ---
> drivers/iommu/riscv/iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-01-17 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 2:46 [PATCH] iommu/riscv: Fixup compile warning guoren
2025-01-03 2:46 ` guoren
2025-01-06 10:31 ` Alexandre Ghiti
2025-01-06 10:31 ` Alexandre Ghiti
2025-01-06 17:47 ` Samuel Holland
2025-01-06 17:47 ` Samuel Holland
2025-01-08 6:47 ` Guo Ren
2025-01-08 6:47 ` Guo Ren
2025-01-10 20:48 ` Tomasz Jeznach
2025-01-10 20:48 ` Tomasz Jeznach
2025-01-10 2:44 ` Charlie Jenkins
2025-01-10 2:44 ` Charlie Jenkins
2025-01-17 7:58 ` Joerg Roedel [this message]
2025-01-17 7:58 ` Joerg Roedel
2025-02-03 19:16 ` patchwork-bot+linux-riscv
2025-02-03 19:16 ` patchwork-bot+linux-riscv
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=Z4oNqjtzYkjRJlYr@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robin.murphy@arm.com \
--cc=tjeznach@rivosinc.com \
--cc=will@kernel.org \
--cc=zong.li@sifive.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 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.