All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
	kernel test robot <dan.carpenter@linaro.org>,
	Thierry Reding <treding@nvidia.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH] drm/tegra: fix potential uninitialized variable use
Date: Tue, 03 Sep 2024 19:25:41 +0300	[thread overview]
Message-ID: <87frqgu2ka.fsf@intel.com> (raw)
In-Reply-To: <dejyfvxyi6fibvld3rdlxf2m4xws7shxvhhkokp6y2jk2djltz@reoqqwov4jg4>

On Tue, 03 Sep 2024, Thierry Reding <thierry.reding@gmail.com> wrote:
> On Mon, Sep 02, 2024 at 07:13:17PM GMT, Jani Nikula wrote:
>> It's likely either output->drm_edid or output->ddc is non-NULL, but
>> avoid the uninitialized variable usage anyway.
>> 
>> Reported-by: kernel test robot <dan.carpenter@linaro.org>
>> Closes: https://lore.kernel.org/r/ZtXLyXxew7z6H2bD@stanley.mountain
>> Fixes: 98365ca74cbf ("drm/tegra: convert to struct drm_edid")
>> Cc: Thierry Reding <treding@nvidia.com>
>> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> Cc: linux-tegra@vger.kernel.org
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/tegra/output.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Do you want to apply this or should I? In the former case:
>
> Acked-by: Thierry Reding <treding@nvidia.com>

Thanks, pushed to drm-misc-next.

BR,
Jani.

-- 
Jani Nikula, Intel

      reply	other threads:[~2024-09-03 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02 16:13 [PATCH] drm/tegra: fix potential uninitialized variable use Jani Nikula
2024-09-03 11:58 ` Thierry Reding
2024-09-03 16:25   ` Jani Nikula [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=87frqgu2ka.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=dan.carpenter@linaro.org \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.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.