From: Mark Brown <broonie@kernel.org>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
srinivas.kandagatla@linaro.org, bgoswami@quicinc.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next 0/2] ASoC: Cleanup deprecated regmap-irq functionality
Date: Thu, 21 Jul 2022 12:22:07 +0100 [thread overview]
Message-ID: <Ytk235u8xWD+vEMB@sirena.org.uk> (raw)
In-Reply-To: <20220721102558.25457-1-aidanmacdonald.0x0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Thu, Jul 21, 2022 at 11:25:56AM +0100, Aidan MacDonald wrote:
> Update two ASoC codec drivers to remove uses of regmap-irq type
> registers, which have recently been deprecated by the "regmap-irq
> cleanups and refactoring" series in linux-next.
>
> Link: https://lore.kernel.org/lkml/20220623211420.918875-1-aidanmacdonald.0x0@gmail.com/
>
> Aidan MacDonald (2):
> sound: soc: codecs: wcd9335: Convert irq chip to config regs
> sound: soc: codecs: wcd938x: Remove spurious type_base from irq chip
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-07-21 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 10:25 Aidan MacDonald
2022-07-21 10:25 ` [PATCH -next 1/2] sound: soc: codecs: wcd9335: Convert irq chip to config regs Aidan MacDonald
2022-07-21 10:25 ` [PATCH -next 2/2] sound: soc: codecs: wcd938x: Remove spurious type_base from irq chip Aidan MacDonald
2022-07-21 11:22 ` Mark Brown [this message]
2022-08-28 21:03 ` [PATCH -next 0/2] ASoC: Cleanup deprecated regmap-irq functionality 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=Ytk235u8xWD+vEMB@sirena.org.uk \
--to=broonie@kernel.org \
--cc=aidanmacdonald.0x0@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--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
all inboxes | Powered by JetHome®