All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org
Cc: tiwai@suse.de, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 0/3] ASoC: codecs: cppcheck warnings
Date: Fri,  6 Aug 2021 01:47:51 +0100	[thread overview]
Message-ID: <162821054282.18754.5123927273200874101.b4-ty@kernel.org> (raw)
In-Reply-To: <20210804192456.278702-1-pierre-louis.bossart@linux.intel.com>

On Wed, 4 Aug 2021 14:24:53 -0500, Pierre-Louis Bossart wrote:
> Two minor corrections for return values, and one more important one
> for max98090 where duplicate reads don't seem necessary.
> 
> Pierre-Louis Bossart (3):
>   ASoC: max98090: remove duplicate status reads and useless assignmment
>   ASoC: mt6359-accdet.c: remove useless assignments
>   ASoC: wcd938x: simplify return value
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: max98090: remove duplicate status reads and useless assignmment
      commit: 221034aca4fdcf8a6552267d2d3aa6825fae29b1
[2/3] ASoC: mt6359-accdet.c: remove useless assignments
      commit: c18abd00333b8b4c6432f4a6789aa02e3b18fdc8
[3/3] ASoC: wcd938x: simplify return value
      commit: 8c62dbcb489aa038fcb9c73faa5c6b56f1f54902

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

      parent reply	other threads:[~2021-08-06  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 19:24 [PATCH 0/3] ASoC: codecs: cppcheck warnings Pierre-Louis Bossart
2021-08-04 19:24 ` [PATCH 1/3] ASoC: max98090: remove duplicate status reads and useless assignmment Pierre-Louis Bossart
2021-08-04 19:24 ` [PATCH 2/3] ASoC: mt6359-accdet.c: remove useless assignments Pierre-Louis Bossart
2021-08-04 19:24 ` [PATCH 3/3] ASoC: wcd938x: simplify return value Pierre-Louis Bossart
2021-08-06  0: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 \
    --in-reply-to=162821054282.18754.5123927273200874101.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@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.