From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.cirrus.com>
Cc: lgirdwood@gmail.com, yung-chuan.liao@linux.intel.com,
pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
shumingf@realtek.com, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 4/4] ASoC: SDCA: Update text of FIXME
Date: Thu, 9 Apr 2026 18:08:10 +0100 [thread overview]
Message-ID: <adfc-q2KTRLIP3q1@sirena.co.uk> (raw)
In-Reply-To: <20260409164328.3999434-5-ckeepax@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
On Thu, Apr 09, 2026 at 05:43:28PM +0100, Charles Keepax wrote:
> A couple of attempts to correct this FIXME have been sent upstream but
> the situation is not quite a simple as the FIXME implies. Update the
> FIXME to include a better description of the situation.
Please don't try to mix versions in the middle of a series, that is just
going to confuse both people and tooling. The versioning applies to the
series as a whole.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-04-09 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:43 [PATCH 0/4] Yet another round of SDCA fixes Charles Keepax
2026-04-09 16:43 ` [PATCH v2 1/4] ASoC: SDCA: Correct kernel doc for sdca_irq_cleanup() Charles Keepax
2026-04-09 16:43 ` [PATCH v2 2/4] ASoC: SDCA: Fix cleanup inversion in class driver Charles Keepax
2026-04-09 16:43 ` [PATCH v2 3/4] ASoC: SDCA: Tidy up irq_enable_flags()/sdca_irq_disable() Charles Keepax
2026-04-09 16:43 ` [PATCH 4/4] ASoC: SDCA: Update text of FIXME Charles Keepax
2026-04-09 17:08 ` Mark Brown [this message]
2026-04-09 18:39 ` Mark Brown
2026-04-10 8:31 ` Charles Keepax
2026-04-09 18:39 ` [PATCH 0/4] Yet another round of SDCA fixes Mark Brown
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=adfc-q2KTRLIP3q1@sirena.co.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=shumingf@realtek.com \
--cc=yung-chuan.liao@linux.intel.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