From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
perex@perex.cz, tiwai@suse.com, lgirdwood@gmail.com,
ckeepax@opensource.cirrus.com, kuninori.morimoto.gx@renesas.com,
linux-kernel@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: codecs: wsa883x: do not set can_multi_write flag
Date: Mon, 5 Jun 2023 14:31:40 +0200 [thread overview]
Message-ID: <ZH3VrC0v4orFUEby@hovoldconsulting.com> (raw)
In-Reply-To: <b3bc0a07-4dcb-4f50-a7b3-91a4a62fac56@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
On Mon, Jun 05, 2023 at 01:24:04PM +0100, Mark Brown wrote:
> On Mon, Jun 05, 2023 at 10:08:34AM +0200, Johan Hovold wrote:
>
> > Is it possible to get also these fixes into 6.4 final?
>
> They're already queued for 6.4.
Indeed they are. Your patch-applied message said "Applied to ...
for-next" and I didn't check your repo before reporting.
Sorry about the noise.
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-06-05 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:46 [PATCH 1/2] ASoC: codecs: wsa883x: do not set can_multi_write flag Srinivas Kandagatla
2023-05-23 15:46 ` [PATCH 2/2] ASoC: codecs: wsa881x: " Srinivas Kandagatla
2023-05-23 16:55 ` [PATCH 1/2] ASoC: codecs: wsa883x: " Mark Brown
2023-05-24 8:51 ` Srinivas Kandagatla
2023-05-24 8:57 ` Mark Brown
2023-05-24 9:42 ` Srinivas Kandagatla
2023-05-24 9:48 ` Mark Brown
2023-05-24 10:09 ` Srinivas Kandagatla
2023-05-24 10:14 ` Mark Brown
2023-05-24 11:28 ` Mark Brown
2023-06-05 8:08 ` Johan Hovold
2023-06-05 12:24 ` Mark Brown
2023-06-05 12:31 ` Johan Hovold [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=ZH3VrC0v4orFUEby@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--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