All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] regmap: maple: Fix uninitialized symbol 'ret' warnings
Date: Fri, 29 Mar 2024 18:38:27 +0000	[thread overview]
Message-ID: <171173750738.1608278.15466912319940390970.b4-ty@kernel.org> (raw)
In-Reply-To: <20240329144630.1965159-1-rf@opensource.cirrus.com>

On Fri, 29 Mar 2024 14:46:30 +0000, Richard Fitzgerald wrote:
> Fix warnings reported by smatch by initializing local 'ret' variable
> to 0.
> 
> drivers/base/regmap/regcache-maple.c:186 regcache_maple_drop()
> error: uninitialized symbol 'ret'.
> drivers/base/regmap/regcache-maple.c:290 regcache_maple_sync()
> error: uninitialized symbol 'ret'.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/1] regmap: maple: Fix uninitialized symbol 'ret' warnings
      commit: eaa03486d932572dfd1c5f64f9dfebe572ad88c0

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2024-03-29 18:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 14:46 [PATCH] regmap: maple: Fix uninitialized symbol 'ret' warnings Richard Fitzgerald
2024-03-29 18:38 ` Mark Brown [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=171173750738.1608278.15466912319940390970.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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.