From: Mark Brown <email@example.com> To: Andy Gross <firstname.lastname@example.org>, Liam Girdwood <email@example.com>, Wesley Cheng <firstname.lastname@example.org>, Bjorn Andersson <email@example.com>, firstname.lastname@example.org, Colin King <email@example.com> Cc: firstname.lastname@example.org, email@example.com Subject: Re: [PATCH][next] regulator: fix null pointer check on regmap Date: Thu, 02 Jul 2020 15:47:07 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On Thu, 2 Jul 2020 12:56:59 +0100, Colin King wrote: > The null pointer check on regmap that checks for a dev_get_regmap failure > is currently returning -ENOENT if the regmap succeeded. Fix this by adding > in the missing ! operator. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: fix null pointer check on regmap commit: 94462138f368a5e079d53d578509276e4366d0c1 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:[~2020-07-02 15:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-02 11:56 Colin King 2020-07-02 15:47 ` 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 \ --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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH][next] regulator: fix null pointer check on regmap' \ /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).