From: Mark Brown <email@example.com> To: Liam Girdwood <firstname.lastname@example.org>, Matti Vaittinen <email@example.com>, firstname.lastname@example.org, Colin King <email@example.com> Cc: Mark Brown <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org Subject: Re: [PATCH][next] regulator: bd9576: Fix uninitializes variable may_have_irqs Date: Wed, 23 Jun 2021 17:08:54 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Tue, 22 Jun 2021 15:47:30 +0100, Colin King wrote: > The boolean variable may_have_irqs is not ininitialized and is > only being set to true in the case where chip is ROHM_CHIP_TYPE_BD9576. > Fix this by ininitialized may_have_irqs to false. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: bd9576: Fix uninitializes variable may_have_irqs commit: ddf275b219ab22bc07c14ac88c290694089dced0 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
prev parent reply other threads:[~2021-06-23 16:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-22 14:47 Colin King 2021-06-22 15:30 ` Vaittinen, Matti 2021-06-23 16:08 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH][next] regulator: bd9576: Fix uninitializes variable may_have_irqs' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).