All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: boris.brezillon@collabora.com, maarten.lankhorst@linux.intel.com,
	dan.carpenter@oracle.com
Cc: Maxime Ripard <maxime@cerno.tech>,
	narmstrong@baylibre.com, airlied@linux.ie, tzimmermann@suse.de,
	mripard@kernel.org, jernej.skrabec@gmail.com,
	dri-devel@lists.freedesktop.org, daniel@ffwll.ch,
	kernel-janitors@vger.kernel.org
Subject: Re: (subset) [PATCH v2] drm/bridge: Avoid uninitialized variable warning
Date: Fri,  8 Jul 2022 13:46:03 +0200	[thread overview]
Message-ID: <165728076204.379115.16118851103019344227.b4-ty@cerno.tech> (raw)
In-Reply-To: <YrrIs3hoGcPVmXc5@kili>

On Mon, 4 Jul 2022 13:55:40 +0300, Dan Carpenter wrote:
> This code works, but technically it uses "num_in_bus_fmts" before it
> has been initialized so it leads to static checker warnings and probably
> KMEMsan warnings at run time.  Initialize the variable to zero to
> silence the warning.
> 
> 

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime@cerno.tech>
To: boris.brezillon@collabora.com, maarten.lankhorst@linux.intel.com,
	dan.carpenter@oracle.com
Cc: narmstrong@baylibre.com, airlied@linux.ie,
	dri-devel@lists.freedesktop.org, kernel-janitors@vger.kernel.org,
	jernej.skrabec@gmail.com, tzimmermann@suse.de,
	Maxime Ripard <maxime@cerno.tech>
Subject: Re: (subset) [PATCH v2] drm/bridge: Avoid uninitialized variable warning
Date: Fri,  8 Jul 2022 13:46:03 +0200	[thread overview]
Message-ID: <165728076204.379115.16118851103019344227.b4-ty@cerno.tech> (raw)
In-Reply-To: <YrrIs3hoGcPVmXc5@kili>

On Mon, 4 Jul 2022 13:55:40 +0300, Dan Carpenter wrote:
> This code works, but technically it uses "num_in_bus_fmts" before it
> has been initialized so it leads to static checker warnings and probably
> KMEMsan warnings at run time.  Initialize the variable to zero to
> silence the warning.
> 
> 

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime

  reply	other threads:[~2022-07-08 11:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 10:55 [PATCH v2] drm/bridge: Avoid uninitialized variable warning Dan Carpenter
2022-07-04 10:55 ` Dan Carpenter
2022-07-08 11:46 ` Maxime Ripard [this message]
2022-07-08 11:46   ` (subset) " Maxime Ripard

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=165728076204.379115.16118851103019344227.b4-ty@cerno.tech \
    --to=maxime@cerno.tech \
    --cc=airlied@linux.ie \
    --cc=boris.brezillon@collabora.com \
    --cc=dan.carpenter@oracle.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=tzimmermann@suse.de \
    /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.