From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: soc-core: Create device_link to ensure correct suspend order
Date: Fri, 5 Jun 2026 17:32:51 +0100 [thread overview]
Message-ID: <e2d7793a-c7ae-42b2-a841-c2a9d3ca1200@sirena.org.uk> (raw)
In-Reply-To: <84d162fc-2b0a-4aac-ad40-2203a277d82f@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 634 bytes --]
On Fri, Jun 05, 2026 at 09:55:07AM +0100, Richard Fitzgerald wrote:
> On 01/06/2026 3:28 pm, Richard Fitzgerald wrote:
> > I think it would be ok to put this into -next and let it get some wider
> > testing before it goes into 7.1 or older.
> I was looking at the Sashiko review for this patch.
> If Sashiko can be trusted, device_links seems to be thoroughly
> booby-trapped.
> Short summary seems to be: only safe way to use them is with the
> STATELESS flag and do manual cleanup.
Yeah, I saw that but didn't put the time in to confirming how reliable
the specific analysis is. The booby trapped bit seems about right
though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-06-05 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 14:28 Richard Fitzgerald
2026-06-02 8:46 ` Charles Keepax
2026-06-02 13:31 ` Mark Brown
2026-06-02 13:34 ` Richard Fitzgerald
2026-06-02 13:46 ` Mark Brown
2026-06-02 13:55 ` Richard Fitzgerald
2026-06-02 14:52 ` Mark Brown
2026-06-05 8:55 ` Richard Fitzgerald
2026-06-05 16:32 ` 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=e2d7793a-c7ae-42b2-a841-c2a9d3ca1200@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@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®