From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: [PATCH 0/3] Re: Internal Mic vs Int Mic
Date: Mon, 20 Dec 2010 14:55:15 +0100 [thread overview]
Message-ID: <4D0F6043.1010506@canonical.com> (raw)
In-Reply-To: <s5hvd2ozk19.wl%tiwai@suse.de>
On 2010-12-20 13:49, Takashi Iwai wrote:
> At Mon, 20 Dec 2010 10:07:38 +0100,
> David Henningsson wrote:
>>
>> To try to clean up a little in the Volume Control namespace, it seems
>> "Int Mic" and "Internal Mic" both mean the same thing. "Internal Mic"
>> seems to be the winning one as it is used in
>> hda_codec.c:hda_get_input_pin_label.
>>
>> So, would a patch that changes every "Int Mic" to "Internal Mic" be
>> appreciated and merged?
>
> Sounds reasonable. Go ahead.
Ok. I also took the liberty of renaming "Ext Mic" and "External Mic" to
just "Mic", which is the de-facto standard for external microphone jacks.
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-12-20 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 9:07 Internal Mic vs Int Mic David Henningsson
2010-12-20 12:49 ` Takashi Iwai
2010-12-20 13:55 ` David Henningsson [this message]
2010-12-20 14:37 ` [PATCH 0/3] " 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=4D0F6043.1010506@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.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