Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
	Jonathan Cavitt <jonathan.cavitt@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH v2 0/2] Sparse errors on the i915_gem_stolen
Date: Mon, 17 Jun 2024 20:42:41 +0200	[thread overview]
Message-ID: <20240617184243.330231-1-andi.shyti@linux.intel.com> (raw)

Hi Jonathan,

Commit 05da7d9f717b ("drm/i915/gem: Downgrade stolen lmem setup
warning") produces two sparse warnings. The first one being a bit
more sever as it might cause a segmentation fault.

The difference between v1 and v2 is that the patch should return
a NULL, which won't cause any issues.

Andi

Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>

Andi Shyti (2):
  drm/i915/gem: Return NULL instead of '0'
  drm/i915/gem: Use the correct format specifier for resource_size_t

 drivers/gpu/drm/i915/gem/i915_gem_stolen.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

-- 
2.45.1


             reply	other threads:[~2024-06-17 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 18:42 Andi Shyti [this message]
2024-06-17 18:42 ` [PATCH v2 1/2] drm/i915/gem: Return NULL instead of '0' Andi Shyti
2024-06-27 13:28   ` Lucas De Marchi
2024-06-17 18:42 ` [PATCH v2 2/2] drm/i915/gem: Use the correct format specifier for resource_size_t Andi Shyti
2024-06-27 13:27   ` Lucas De Marchi
2024-06-17 19:37 ` ✓ Fi.CI.BAT: success for Sparse errors on the i915_gem_stolen (rev2) Patchwork
2024-06-18  8:43 ` ✓ Fi.CI.IGT: " Patchwork
2024-06-18 19:34 ` [PATCH v2 0/2] Sparse errors on the i915_gem_stolen Cavitt, Jonathan
2024-06-19 10:56   ` Andi Shyti

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=20240617184243.330231-1-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jonathan.cavitt@intel.com \
    --cc=lucas.demarchi@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