diff options
author | Takashi Sakamoto <o-takashi@sakamocchi.jp> | 2016-09-24 19:28:23 +0900 |
---|---|---|
committer | Takashi Iwai <tiwai@suse.de> | 2016-09-25 22:16:49 +0200 |
commit | 318824d3d0795309b448563faa698d3c02035db4 (patch) | |
tree | 796ddd0e7a698b384d350108873ded3bcc14e920 /scripts/dtc/dtc-parser.y | |
parent | 0da325afbdb80098e014b83937372e3eef6872d5 (diff) |
ALSA: control: cage TLV_DB_RANGE_HEAD in kernel land because it was obsoleted
In commit bf1d1c9b6179 ("ALSA: tlv: add DECLARE_TLV_DB_RANGE()"), the new
macro was added so that "dB range information can be specified without
having to count the items manually for TLV_DB_RANGE_HEAD()". In short,
TLV_DB_RANGE_HEAD macro was obsoleted.
In commit 46e860f76804 ("ALSA: rename TLV-related macros so that they're
friendly to user applications"), TLV-related macros are exposed for
applications in user land to get content of data structured by
Type/Length/Value shape. The commit managed to expose TLV-related macros
as many as possible, while obsoleted TLV_DB_RANGE_HEAD() was included to
the list of exposed macros.
This situation brings some confusions to application developers because
they might think all exposed macros have their own purpose and useful for
applications.
For the reason, this commit moves TLV_DB_RANGE_HEAD macro from UAPI header
to a header for kernel land, again. The above commit is done within the
same development period for kernel 4.9, thus not published yet. This
commit might certainly brings no confusions to user land.
Reference: commit bf1d1c9b6179 ("ALSA: tlv: add DECLARE_TLV_DB_RANGE()")
Reference: commit 46e860f76804 ("ALSA: rename TLV-related macros so that they're friendly to user applications")
Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'scripts/dtc/dtc-parser.y')
0 files changed, 0 insertions, 0 deletions