From: Andi Shyti <andi.shyti@linux.intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
chris@chris-wilson.co.uk, andrzej.hajda@intel.com,
rodrigo.vivi@intel.com, mchehab@kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Use "%zu" to format size_t
Date: Mon, 2 Jan 2023 15:27:51 +0100 [thread overview]
Message-ID: <Y7LpskDkbpuybI17@ashyti-mobl2.lan> (raw)
In-Reply-To: <20221230183500.20553-1-nirmoy.das@intel.com>
On Fri, Dec 30, 2022 at 07:35:00PM +0100, Nirmoy Das wrote:
> Switch to %zu for printing size_t which will
> fix compilation warning for 32-bit build.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
> ---
> drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> index e767791e40e0..114443096841 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> @@ -238,7 +238,7 @@ static int shmem_get_pages(struct drm_i915_gem_object *obj)
> goto rebuild_st;
> } else {
> dev_warn(i915->drm.dev,
> - "Failed to DMA remap %lu pages\n",
> + "Failed to DMA remap %zu pages\n",
> obj->base.size >> PAGE_SHIFT);
> goto err_pages;
> }
> --
> 2.38.0
next prev parent reply other threads:[~2023-01-02 14:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 18:35 [Intel-gfx] [PATCH] drm/i915: Use "%zu" to format size_t Nirmoy Das
2022-12-30 19:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-12-30 19:37 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-03 8:11 ` Gwan-gyeong Mun
2023-01-03 9:03 ` Das, Nirmoy
2023-01-02 13:20 ` [Intel-gfx] [PATCH] " Gwan-gyeong Mun
2023-01-02 14:27 ` Andi Shyti [this message]
2023-01-04 12:51 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Use "%zu" to format size_t (rev2) Patchwork
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=Y7LpskDkbpuybI17@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mchehab@kernel.org \
--cc=nirmoy.das@intel.com \
--cc=rodrigo.vivi@intel.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