From: Vinod Koul <vinod.koul@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Re: [PATCH 0/3] ASoC: remove SND_SOC_BYTES_EXT
Date: Wed, 18 Nov 2015 23:49:53 +0530 [thread overview]
Message-ID: <20151118181953.GX25173@localhost> (raw)
In-Reply-To: <s5hlh9ve7n0.wl-tiwai@suse.de>
On Wed, Nov 18, 2015 at 02:53:23PM +0100, Takashi Iwai wrote:
> On Wed, 18 Nov 2015 14:39:09 +0100,
> Vinod Koul wrote:
> >
> > The SND_SOC_BYTES_TLV and SND_SOC_BYTES_EXT provide similar functionality,
> > with only difference that SND_SOC_BYTES_EXT have limitations of 512 bytes
> > as parameters whereas no such restrictions on SND_SOC_BYTES_TLV
> >
> > So remove SND_SOC_BYTES_EXT and update users to use SND_SOC_BYTES_TLV
>
> Hmm, won't this break user-space? Both use the difference access
> methods, so I wonder how they can be kept compatible.
Yes they will, so should we then keep these and mark SND_SOC_BYTES_EXT
depricated ..?
Mark what should we do with these
--
~Vinod
next prev parent reply other threads:[~2015-11-18 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 13:39 [PATCH 0/3] ASoC: remove SND_SOC_BYTES_EXT Vinod Koul
2015-11-18 13:39 ` [PATCH 1/3] ASoC: Intel: Hsw: Move driver to use SND_SOC_BYTES_TLV Vinod Koul
2015-11-19 3:22 ` Keyon
2015-11-19 6:56 ` Han Lu
2015-11-18 13:39 ` [PATCH 2/3] ASoC: wm5102: " Vinod Koul
2015-11-19 14:22 ` Charles Keepax
[not found] ` <201511182144.8dDI1Wfc%fengguang.wu@intel.com>
2015-11-20 17:07 ` Vinod Koul
2015-11-18 13:39 ` [PATCH 3/3] ASoC: core: remove SND_SOC_BYTES_EXT Vinod Koul
2015-11-18 13:53 ` [PATCH 0/3] ASoC: " Takashi Iwai
2015-11-18 18:19 ` Vinod Koul [this message]
2015-11-21 14:08 ` Mark Brown
2015-11-22 16:17 ` Vinod Koul
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=20151118181953.GX25173@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@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).