Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Cezary Rojewski <cezary.rojewski@intel.com>
Cc: tiwai@suse.com, perex@perex.cz, amade@asmblr.net,
	 linux-sound@vger.kernel.org
Subject: Re: [PATCH 0/5] ASoC: Intel: catpt: IPC log improvements and code simplification
Date: Mon, 15 Dec 2025 22:58:52 +0900	[thread overview]
Message-ID: <176580713295.161056.3659304742036550658.b4-ty@kernel.org> (raw)
In-Reply-To: <20251212103858.110701-1-cezary.rojewski@intel.com>

On Fri, 12 Dec 2025 11:38:53 +0100, Cezary Rojewski wrote:
> Entire patchset provides no new features and does not alter the code
> from functional (user) perspective.
> 
> The first two improve IPC-error logging 'mechanism' and align the
> catpt-driver with what's done in another Intel's driver: the avs-driver.
> In essence, no need to log the error in every function, let the common
> handler do so instead.
> 
> [...]

Applied to

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

Thanks!

[1/5] ASoC: Intel: catpt: Move IPC error messages one level down
      commit: 384b13038715f16713d1b2bfe5fb927c8437e48b
[2/5] ASoC: Intel: catpt: Update CATPT_IPC_ERROR macro
      commit: eded4483b8a21eaeb0886ef6f961ccf4e0d9c976
[3/5] ASoC: Intel: catpt: Simplify catpt_stream_read_position()
      commit: d44f62b09b1e97baee3b10484a1c3c203bb83caf
[4/5] ASoC: Intel: catpt: Specify image names in the device descriptor
      commit: e97e07138f956a551895a9556d1a929978a5346d
[5/5] ASoC: Intel: catpt: Drop superfluous space in PCM code
      commit: aa30193af8873b3ccfd70a4275336ab6cbd4e5e6

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:[~2025-12-15 13:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-12 10:38 [PATCH 0/5] ASoC: Intel: catpt: IPC log improvements and code simplification Cezary Rojewski
2025-12-12 10:38 ` [PATCH 1/5] ASoC: Intel: catpt: Move IPC error messages one level down Cezary Rojewski
2025-12-12 10:38 ` [PATCH 2/5] ASoC: Intel: catpt: Update CATPT_IPC_ERROR macro Cezary Rojewski
2025-12-12 10:38 ` [PATCH 3/5] ASoC: Intel: catpt: Simplify catpt_stream_read_position() Cezary Rojewski
2025-12-12 10:38 ` [PATCH 4/5] ASoC: Intel: catpt: Specify image names in the device descriptor Cezary Rojewski
2025-12-12 10:38 ` [PATCH 5/5] ASoC: Intel: catpt: Drop superfluous space in PCM code Cezary Rojewski
2025-12-15 13:58 ` 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=176580713295.161056.3659304742036550658.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=amade@asmblr.net \
    --cc=cezary.rojewski@intel.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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