mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH 0/5] ASoC: cs35l56: Code improvements
Date: Mon, 17 Apr 2023 21:27:41 +0100	[thread overview]
Message-ID: <168176326169.1296984.12735339184719682836.b4-ty@kernel.org> (raw)
In-Reply-To: <20230414133753.653139-1-rf@opensource.cirrus.com>

On Fri, 14 Apr 2023 14:37:48 +0100, Richard Fitzgerald wrote:
> Various code improvements. These remove redundant code and
> clean up less-than-optimal original implementations.
> 
> Simon Trimmer (5):
>   ASoC: cs35l56: Rework IRQ allocation
>   ASoC: cs35l56: Allow a wider range for reset pulse width
>   ASoC: cs35l56: Wait for init_complete in cs35l56_component_probe()
>   ASoC: cs35l56: Remove redundant dsp_ready_completion
>   ASoC: cs35l56: Don't return a value from cs35l56_remove()
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: cs35l56: Rework IRQ allocation
      commit: 7d72351a4ef6e1e763bccc24d43c44ffbe1a1555
[2/5] ASoC: cs35l56: Allow a wider range for reset pulse width
      commit: b82396122b028a07ce2977e3f33123d7ab526d91
[3/5] ASoC: cs35l56: Wait for init_complete in cs35l56_component_probe()
      commit: 440c2d38950f738d7a35d3d29533728e74586d54
[4/5] ASoC: cs35l56: Remove redundant dsp_ready_completion
      commit: 4be476830bf96c0095e4e1acdfc12081aa0fb165
[5/5] ASoC: cs35l56: Don't return a value from cs35l56_remove()
      commit: 9ed4c762e214a6592184d0dd65b6db86ad30e6d5

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:[~2023-04-17 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 13:37 Richard Fitzgerald
2023-04-14 13:37 ` [PATCH 1/5] ASoC: cs35l56: Rework IRQ allocation Richard Fitzgerald
2023-04-14 13:37 ` [PATCH 2/5] ASoC: cs35l56: Allow a wider range for reset pulse width Richard Fitzgerald
2023-04-14 13:37 ` [PATCH 3/5] ASoC: cs35l56: Wait for init_complete in cs35l56_component_probe() Richard Fitzgerald
2023-04-14 13:37 ` [PATCH 4/5] ASoC: cs35l56: Remove redundant dsp_ready_completion Richard Fitzgerald
2023-04-14 13:37 ` [PATCH 5/5] ASoC: cs35l56: Don't return a value from cs35l56_remove() Richard Fitzgerald
2023-04-17 20:27 ` 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=168176326169.1296984.12735339184719682836.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®