Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: ALSA ML <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>,
	pardha.saradhi.kesapragada@intel.com, cezary.rojewski@intel.com,
	Puneeth Prabhu <puneethx.prabhu@intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Patches Audio <patches.audio@intel.com>,
	gustaw.lewandowski@intel.com
Subject: Re: [PATCH] ASoC: topology: Increase SND_SOC_TPLG_NUM_TEXTS to 32
Date: Fri, 20 Jul 2018 15:46:25 +0100	[thread overview]
Message-ID: <20180720144625.GJ10784@sirena.org.uk> (raw)
In-Reply-To: <cc342153-28fd-85bf-acab-a695882af115@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 491 bytes --]

On Fri, Jul 20, 2018 at 08:58:07AM -0500, Pierre-Louis Bossart wrote:

> Agree with Mark on both points (de-duplication needed and backwards
> compatibility). If we are going to respin a new version, there are a couple
> of known limitations we may want to fix as well, such as the limitation to 8
> channels and others I will remember once I've had more coffee.

Actually it looks like the duplication isn't a thing, I can't see the
definition the patch was intended to modify in upstream.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2018-07-20 14:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 10:27 [PATCH] ASoC: topology: Increase SND_SOC_TPLG_NUM_TEXTS to 32 Puneeth Prabhu
2018-07-20 10:27 ` [PATCH] topology: ABI: " Puneeth Prabhu
2018-07-20 12:39   ` Mark Brown
2018-07-20 12:38 ` [PATCH] ASoC: topology: " Mark Brown
2018-07-20 13:58   ` Pierre-Louis Bossart
2018-07-20 14:46     ` Mark Brown [this message]
2018-07-20 16:02 ` Pierre-Louis Bossart

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=20180720144625.GJ10784@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=cezary.rojewski@intel.com \
    --cc=gustaw.lewandowski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pardha.saradhi.kesapragada@intel.com \
    --cc=patches.audio@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=puneethx.prabhu@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