From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: [alsa-lib][PATCH] ctl: improve documentation of APIs to add an element set
Date: Sat, 9 Jul 2016 22:18:30 +0900 [thread overview]
Message-ID: <5780F9A6.2020002@sakamocchi.jp> (raw)
In-Reply-To: <s5hbn27jpqp.wl-tiwai@suse.de>
On Jul 9 2016 15:21, Takashi Iwai wrote:
> On Sat, 09 Jul 2016 03:44:19 +0200,
> Takashi Sakamoto wrote:
>>
>> Currently, documentation of APIs to add an element set describes causes of
>> errors partly. But it gives an opinion to describe them thoroughly. This
>> is not good for users.
>>
>> This commit changes the documentation so that it partly describes the
>> causes.
>>
>> Signed-off-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
>
> Applied, thanks.
Thanks.
As a rest of issues about the new APIs, I think it better to change
their names. Currently, I named them by adding '_set' suffix to names of
old APIs; i.e.
'snd_ctl_elem_add_integer' -> 'snd_ctl_elem_add_integer_set'.
The names give an opinion to users that these APIs are to add something
to existent control elements. The functionalities of the APIs are add
some elements to something accessed via CTL handler; practically it's a
control instance for a sound card, accessed via 'hw' plugin.
Thus, I think it better to rename them; i.e.
'snd_ctl_add_integer_elem_set'. Could I ask your opinion about this?
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2016-07-09 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-09 1:44 [alsa-lib][PATCH] ctl: improve documentation of APIs to add an element set Takashi Sakamoto
2016-07-09 6:21 ` Takashi Iwai
2016-07-09 13:18 ` Takashi Sakamoto [this message]
2016-07-11 10:38 ` Takashi Iwai
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=5780F9A6.2020002@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--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