From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH 1/3] topology: use inclusive language for bclk
Date: Tue, 8 Sep 2020 09:41:34 -0500 [thread overview]
Message-ID: <70a2012f-aa8b-52db-7694-592677d7171c@linux.intel.com> (raw)
In-Reply-To: <20200908143504.GD5551@sirena.org.uk>
On 9/8/20 9:35 AM, Mark Brown wrote:
> On Tue, Sep 08, 2020 at 08:39:13AM -0500, Pierre-Louis Bossart wrote:
>
>>>> - __u8 bclk_master; /* SND_SOC_TPLG_BCLK_ value */
>>>> + __u8 bclk_provider; /* SND_SOC_TPLG_BCLK_ value */
>
>>> Is it 100% compatible? Note that the uapi/* header is a copy from the
>>> kernel header, and it means that we'll change the same for the kernel,
>>> too.
>
>> It's absolutely 100% compatible by design.
>> I was planning to update the kernel uapi header to align changes, but the
>> volume of code is much lower on the alsa-lib side. Will resubmit with the
>> preferred provider/consumer wording.
>
> It's binary compatible but it'd break the build for any existing code
> using the UAPI headers.
Sorry, I don't fully get the comment. Aren't the uapi headers copied
into each software tree that relies on them?
next prev parent reply other threads:[~2020-09-08 14:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 20:10 [RFC PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology Pierre-Louis Bossart
2020-09-03 20:10 ` [RFC PATCH 1/3] topology: use inclusive language for bclk Pierre-Louis Bossart
2020-09-04 9:10 ` Takashi Iwai
2020-09-08 13:39 ` Pierre-Louis Bossart
2020-09-08 14:35 ` Mark Brown
2020-09-08 14:41 ` Pierre-Louis Bossart [this message]
2020-09-08 14:45 ` Jaroslav Kysela
2020-09-08 17:28 ` Mark Brown
2020-09-03 20:10 ` [RFC PATCH 2/3] topology: use inclusive language for fsync Pierre-Louis Bossart
2020-09-03 20:10 ` [RFC PATCH 3/3] topology: use inclusive language in documentation Pierre-Louis Bossart
2020-09-03 20:42 ` [RFC PATCH 0/3] alsa-lib/ASoC: use inclusive language for bclk/fsync/topology Jaroslav Kysela
2020-09-03 21:32 ` Pierre-Louis Bossart
2020-09-04 8:50 ` Mark Brown
2020-09-08 13:36 ` 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=70a2012f-aa8b-52db-7694-592677d7171c@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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