From: Cezary Rojewski <cezary.rojewski@intel.com>
To: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
Cc: Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
Venkata Prasad Potturu <venkataprasad.potturu@amd.com>,
Jaroslav Kysela <perex@perex.cz>, "Takashi Iwai" <tiwai@suse.com>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Mario Limonciello <mario.limonciello@amd.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
<linux-sound@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH v2 4/6] ASoC: amd: acp: Unify code style for platform_device_id array
Date: Mon, 20 Jul 2026 09:05:35 +0200 [thread overview]
Message-ID: <438e48da-b559-4f08-b12b-078610135550@intel.com> (raw)
In-Reply-To: <08137cf5b3cdd0cc2e00da32256664f3cb9b1e4e.1784528081.git.u.kleine-koenig@baylibre.com>
On 7/20/2026 8:23 AM, Uwe Kleine-König (The Capable Hub) wrote:
> - Add a trailing comma for initializers unless the closing brace is on
> the same line and for the list terminator;
> - Use a single space in the list terminator;
>
> Acked-by: Cezary Rojewski <cezary.rojewski@intel.com>
Perhaps I should have been more clear in my previous response [1] - I
expected the sound/soc/intel/avs changes be separated and then ACK tag
can be freely added _only_ to those (avs-driver) changes. I do not ACK
non-Intel patches.
[1]:
https://lore.kernel.org/linux-sound/28c0e1ae-e2a4-43e8-8be9-c05f8cbeecdb@intel.com/
> Signed-off-by: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>
next prev parent reply other threads:[~2026-07-20 7:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 6:23 [PATCH v2 0/6] ASoC: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-20 6:23 ` [PATCH v2 1/6] ASoC: codecs: mt6357: Drop unused assignment of platform_device_id driver data Uwe Kleine-König (The Capable Hub)
2026-07-20 6:23 ` [PATCH v2 2/6] ASoC: renesas: fsi: Drop platform probing metadata Uwe Kleine-König (The Capable Hub)
2026-07-20 23:12 ` Kuninori Morimoto
2026-07-20 6:23 ` [PATCH v2 3/6] ASoC: amd: acp: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-21 3:48 ` Mukunda,Vijendar
2026-07-20 6:23 ` [PATCH v2 4/6] ASoC: amd: acp: Unify code style for platform_device_id array Uwe Kleine-König (The Capable Hub)
2026-07-20 7:05 ` Cezary Rojewski [this message]
2026-07-20 11:32 ` Uwe Kleine-König (The Capable Hub)
2026-07-21 3:49 ` Mukunda,Vijendar
2026-07-20 6:23 ` [PATCH v2 5/6] ASoC: Use named initializers for platform_device_id arrays Uwe Kleine-König (The Capable Hub)
2026-07-20 8:23 ` Charles Keepax
2026-07-30 11:14 ` Péter Ujfalusi
2026-07-20 6:23 ` [PATCH v2 6/6] ASOC: Unify code style " Uwe Kleine-König (The Capable Hub)
2026-07-22 17:55 ` Cezary Rojewski
2026-07-23 5:30 ` Uwe Kleine-König (The Capable Hub)
2026-07-23 10:28 ` Cezary Rojewski
2026-07-27 23:12 ` [PATCH v2 0/6] ASoC: Use named initializers " Mark Brown
2026-07-30 10:42 ` 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=438e48da-b559-4f08-b12b-078610135550@intel.com \
--to=cezary.rojewski@intel.com \
--cc=Vijendar.Mukunda@amd.com \
--cc=broonie@kernel.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=gpiccoli@igalia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=venkataprasad.potturu@amd.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®