From: Cezary Rojewski <cezary.rojewski@intel.com>
To: Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: <linux-sound@vger.kernel.org>, <tiwai@suse.com>, <perex@perex.cz>,
<amade@asmblr.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] ASoC: core: Create new components in sane state
Date: Tue, 13 Oct 2026 13:24:24 +0200 [thread overview]
Message-ID: <40696247-e763-40d8-9d4e-338047cdd4fe@intel.com> (raw)
In-Reply-To: <ed059f1e-2390-4e1d-bd1a-cff08a3441ad@sirena.org.uk>
On 10/13/2026 12:53 PM, Mark Brown wrote:
> On Mon, Oct 12, 2026 at 11:52:45PM +0000, Kuninori Morimoto wrote:
>
>> I would like to review this patch, but unfortunately I'm busy this week.
>> Actually, I'm now posting cleanup snd_soc_component_xxx(),
>> which has many steps, and is now under progress.
>
>> I will review your patch next week, but I guess some of them (= not all)
>> are conflicts to mine...
>
> Ah, unfortunately I already applied it since we're in the last week
> before the merge window and it didn't get a reply - sorry about that.
I do not see it applied to the for-next.
Obviously I'd appreciate the merge as the gap mentioned in the
cover-letter is there and the framework should sanitize the object
before returning it.
At the same time, I'm here to help with any conflicts should any arise.
next prev parent reply other threads:[~2026-10-13 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 13:33 [PATCH 0/7] ASoC: core: Create new components in sane state Cezary Rojewski
2026-10-07 13:33 ` [PATCH 1/7] ASoC: core: Add component constructor Cezary Rojewski
2026-10-07 13:33 ` [PATCH 2/7] ASoC: core: Rename and export soc_component_add() Cezary Rojewski
2026-10-07 13:33 ` [PATCH 3/7] ASoC: dmaengine: Switch to snd_snd_component_new() Cezary Rojewski
2026-10-07 13:33 ` [PATCH 4/7] ASoC: topology-test: " Cezary Rojewski
2026-10-07 13:33 ` [PATCH 5/7] ASoC: Intel: catpt: " Cezary Rojewski
2026-10-07 13:33 ` [PATCH 6/7] ASoC: Intel: avs: " Cezary Rojewski
2026-10-07 13:33 ` [PATCH 7/7] ASoC: core: Remove unused component-register members Cezary Rojewski
2026-10-12 22:58 ` [PATCH 0/7] ASoC: core: Create new components in sane state Mark Brown
2026-10-12 23:52 ` Kuninori Morimoto
2026-10-13 10:53 ` Mark Brown
2026-10-13 11:24 ` Cezary Rojewski [this message]
2026-10-13 12:44 ` Mark Brown
2026-10-14 3:08 ` Kuninori Morimoto
2026-10-14 8:06 ` Cezary Rojewski
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=40696247-e763-40d8-9d4e-338047cdd4fe@intel.com \
--to=cezary.rojewski@intel.com \
--cc=amade@asmblr.net \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--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