From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: Stefan Binding <sbinding@opensource.cirrus.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v1 0/2] ALSA: cs35l41: prevent old firmwares using unsupported commands
Date: Fri, 22 Sep 2023 16:42:10 +0200 [thread overview]
Message-ID: <875y42clrx.wl-tiwai@suse.de> (raw)
In-Reply-To: <8b5a22bf-73e3-45ca-b61b-38482c9caa39@sirena.org.uk>
On Fri, 22 Sep 2023 16:38:28 +0200,
Mark Brown wrote:
>
> On Fri, Sep 22, 2023 at 04:35:45PM +0200, Takashi Iwai wrote:
> > Stefan Binding wrote:
>
> > > This chain is based on Mark's branch, since the api change was made to
>
> The term is patch series.
>
> > > the function in sound/soc/codecs/cs35l41-lib.c.
>
> > I'd need a PR from Mark before applying those, then.
>
> Or if they're 6.7 stuff I guess I could just carry them.
Yes, that's another option. But there are already changes for HDA
cs35l41 stuff for 6.7, and you might need to pull from my for-next
branch beforehand. A bit messy in either way.
thanks,
Takashi
next prev parent reply other threads:[~2023-09-22 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 14:28 [PATCH v1 0/2] ALSA: cs35l41: prevent old firmwares using unsupported commands Stefan Binding
2023-09-22 14:28 ` [PATCH v1 1/2] ALSA: hda: cs35l41: Remove unnecessary boolean state variable firmware_running Stefan Binding
2023-09-22 14:28 ` [PATCH v1 2/2] ALSA: cs35l41: Fix for old systems which do not support command Stefan Binding
2023-09-22 14:30 ` Mark Brown
2023-09-22 14:35 ` [PATCH v1 0/2] ALSA: cs35l41: prevent old firmwares using unsupported commands Takashi Iwai
2023-09-22 14:38 ` Mark Brown
2023-09-22 14:42 ` Takashi Iwai [this message]
2023-09-22 14:44 ` Stefan Binding
2023-09-22 14:48 ` Mark Brown
2023-09-22 14:53 ` Takashi Iwai
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=875y42clrx.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--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