From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Dragos Tarcatu <dragos_tarcatu@mentor.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Jaska Uimonen <jaska.uimonen@intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
Subject: Re: [alsa-devel] Applied "ASoC: SOF: topology: Fix bytes control size checks" to the asoc tree
Date: Wed, 6 Nov 2019 10:49:20 -0600 [thread overview]
Message-ID: <14d026ab-a898-358e-34ea-4f73d6c0fc0a@linux.intel.com> (raw)
In-Reply-To: <20191106162927.GC11849@sirena.co.uk>
On 11/6/19 10:29 AM, Mark Brown wrote:
> On Wed, Nov 06, 2019 at 04:21:46PM +0000, Mark Brown wrote:
>> The patch
>>
>> ASoC: SOF: topology: Fix bytes control size checks
>>
>> has been applied to the asoc tree at
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.4
>
> It's not immediately obvious if something similar is needed for -next,
> the relevant code has been redone since v5.4 was branched off. If
> something is needed someone will have to send something.
I checked that the patch applies even before Jaska's October rework,
where the same bug was present. so in theory picking this fix for
5.2..5.4 would work as usual.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-06 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 14:58 [alsa-devel] [PATCH] ASoC: SOF: topology: Fix bytes control size checks Pierre-Louis Bossart
2019-11-06 16:21 ` [alsa-devel] Applied "ASoC: SOF: topology: Fix bytes control size checks" to the asoc tree Mark Brown
2019-11-06 16:29 ` Mark Brown
2019-11-06 16:49 ` Pierre-Louis Bossart [this message]
2019-11-06 16:54 ` Mark Brown
2019-11-06 18:15 ` Pierre-Louis Bossart
2019-11-07 13:13 ` 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=14d026ab-a898-358e-34ea-4f73d6c0fc0a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dragos_tarcatu@mentor.com \
--cc=jaska.uimonen@intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).