From: Kees Cook <kees@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
Emanuele Ghidoli <ghidoliemanuele@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Emanuele Ghidoli <emanuele.ghidoli@toradex.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: soc-core: reset rtd->num_components after allocation
Date: Thu, 12 Nov 2026 09:33:48 -0800 [thread overview]
Message-ID: <202611120930.442D702AF@keescook> (raw)
In-Reply-To: <853110dc-2ab9-4271-9e81-20ce5068ecc0@sirena.org.uk>
On Wed, Nov 11, 2026 at 01:09:25PM +0000, Mark Brown wrote:
> Please fix your mail client to word wrap within paragraphs at something
> substantially less than 80 columns. Doing this makes your messages much
> easier to read and reply to.
Yeah, this is a standing problem with K9-Mail, which is what I have on
my phone. I only use it when I'm AFK but I need to reply to something
urgently, such as when I break what looked like basically all soc sound :(
All the other android clients don't really seem to measure up, except
for this particular gap. :( I'll try to remember to manually wrap lines
in the future.
--
Kees Cook
next prev parent reply other threads:[~2026-11-12 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 10:25 [PATCH] ASoC: soc-core: reset rtd->num_components after allocation Emanuele Ghidoli
2026-11-09 11:07 ` Takashi Iwai
2026-11-10 11:47 ` Takashi Iwai
2026-11-11 5:50 ` Kees Cook
2026-11-11 5:59 ` Kees Cook
2026-11-11 10:28 ` Emanuele Ghidoli
2026-11-12 17:27 ` Kees Cook
2026-11-11 13:09 ` Mark Brown
2026-11-12 17:33 ` Kees Cook [this message]
2026-11-10 9:57 ` Jan Remes
2026-11-10 17:45 ` Mark Brown
2026-11-11 10:06 ` Alexander Stein
2026-11-11 12:26 ` Cosmin-Gabriel Tanislav
-- strict thread matches above, loose matches on Subject: below --
2026-11-10 22:01 Rujbin
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=202611120930.442D702AF@keescook \
--to=kees@kernel.org \
--cc=broonie@kernel.org \
--cc=emanuele.ghidoli@toradex.com \
--cc=ghidoliemanuele@gmail.com \
--cc=gustavoars@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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.