From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Kirill Marinushkin <k.marinushkin@gmail.com>
Cc: alsa-devel@alsa-project.org,
Pan Xiuli <xiuli.pan@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [alsa-devel] Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree
Date: Mon, 12 Mar 2018 18:29:37 -0500 [thread overview]
Message-ID: <4780c8aa-face-d811-3bd8-7c2c2ea85eb6@linux.intel.com> (raw)
In-Reply-To: <20180312161455.GD2186@sirena.org.uk>
On 3/12/18 11:14 AM, Mark Brown wrote:
> On Mon, Feb 26, 2018 at 07:34:07PM +0100, Kirill Marinushkin wrote:
>> Hello Mark Brown, Pan Xiuli,
>>
>> As far as I understand, the suggested commit *breaks* the functionality instead
>> of fixing it, and should not be applied. Please correct me if I am wrong.
>
> This discussion ground to a halt a bit (nobody from Intel seems to have
> looked at Kirill's patches?) so I'm going to drop this patch for now,
> I'll keep a copy around at test/topology.
Sorry, we did look at Kirill's patches but wanted to test further, and
of course we are caught in the middle of a release.
It's fine to drop this for now.
prev parent reply other threads:[~2018-03-12 23:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519336888-71831-1-git-send-email-xiuli.pan@linux.intel.com>
2018-02-26 11:17 ` Applied "ASoC: topology: Fix logical inversion in set_link_hw_format()" to the asoc tree Mark Brown
2018-02-26 18:34 ` Kirill Marinushkin
2018-02-26 19:47 ` Mark Brown
2018-02-27 4:38 ` Kirill Marinushkin
2018-02-27 2:30 ` [alsa-devel] " Pierre-Louis Bossart
2018-02-27 4:50 ` Kirill Marinushkin
2018-02-27 10:38 ` Mark Brown
2018-02-27 15:13 ` Pierre-Louis Bossart
2018-02-27 15:57 ` Mark Brown
2018-02-28 6:22 ` Pierre-Louis Bossart
2018-03-12 16:14 ` Mark Brown
2018-03-12 23:29 ` Pierre-Louis Bossart [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=4780c8aa-face-d811-3bd8-7c2c2ea85eb6@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=k.marinushkin@gmail.com \
--cc=stable@vger.kernel.org \
--cc=xiuli.pan@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