All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, intel-gfx@lists.freedesktop.org
Subject: Re: Apply fc7bf4c0d65a342b29fe38c332db3fe900b481b9 to 5.15
Date: Sat, 6 Dec 2025 19:37:55 -0500	[thread overview]
Message-ID: <aTTMYz_n-9ck-tSo@laps> (raw)
In-Reply-To: <20251204001352.GB468348@ax162>

On Wed, Dec 03, 2025 at 05:13:52PM -0700, Nathan Chancellor wrote:
>Hi stable folks,
>
>Please apply commit fc7bf4c0d65a ("drm/i915/selftests: Fix inconsistent
>IS_ERR and PTR_ERR") to 5.15, where it resolves a couple of instances of
>-Wuninitialized with clang-21 or newer that were introduced by commit
>cdb35d1ed6d2 ("drm/i915/gem: Migrate to system at dma-buf attach time
>(v7)") in 5.15.
>
>  In file included from drivers/gpu/drm/i915/gem/i915_gem_dmabuf.c:329:
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c:105:18: error: variable 'dmabuf' is uninitialized when used here [-Werror,-Wuninitialized]
>    105 |                        PTR_ERR(dmabuf));
>        |                                ^~~~~~
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c:94:24: note: initialize the variable 'dmabuf' to silence this warning
>     94 |         struct dma_buf *dmabuf;
>        |                               ^
>        |                                = NULL
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c:161:18: error: variable 'dmabuf' is uninitialized when used here [-Werror,-Wuninitialized]
>    161 |                        PTR_ERR(dmabuf));
>        |                                ^~~~~~
>  drivers/gpu/drm/i915/gem/selftests/i915_gem_dmabuf.c:149:24: note: initialize the variable 'dmabuf' to silence this warning
>    149 |         struct dma_buf *dmabuf;
>        |                               ^
>        |                                = NULL
>
>It applies and builds cleanly for me. If there are any issues, please
>let me know.

Queued up, thanks.

-- 
Thanks,
Sasha

      reply	other threads:[~2025-12-07  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04  0:13 Apply fc7bf4c0d65a342b29fe38c332db3fe900b481b9 to 5.15 Nathan Chancellor
2025-12-07  0:37 ` Sasha Levin [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=aTTMYz_n-9ck-tSo@laps \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nathan@kernel.org \
    --cc=stable@vger.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.