From: Kirill Marinushkin <k.marinushkin@gmail.com>
To: Andrew Chant <achant@google.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches
Date: Mon, 26 Mar 2018 23:13:49 +0200 [thread overview]
Message-ID: <bb64a7f3-1664-65cc-871d-da7d5952a864@gmail.com> (raw)
In-Reply-To: <CANVWZtF6B_Bnv+tGfUVVkjE8PhBQXSMqTdUBa-n1D+uMeVh4=Q@mail.gmail.com>
On 03/26/18 22:41, Andrew Chant wrote:
> On Mon, Mar 26, 2018 at 11:32 AM, Kirill Marinushkin
> <k.marinushkin@gmail.com> wrote:
>> I faced 2 problems:
>>
>> * the clock source validity was displayed as [O]. I thought it is a zero, which is the opposite from the real state
>> * I couldn't find how to turn the processing feature on. The help doesn't say anything about it
> A recent patch of mine changed clock source validity from a mixer to a
> global control, so it should no longer show up in alsamixer.
Hello Andrew,
Nice! One of the problems is solved. However, the second problem is still actual.
As you had a recent experience with alsamixer, what is your opinion?
Best Regards,
Kirill
next prev parent reply other threads:[~2018-03-26 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 5:11 [RFC, alsa-utils] RFC: alsamixer: Improve description of playback switches Kirill Marinushkin
2018-03-26 7:38 ` Takashi Iwai
2018-03-26 18:32 ` Kirill Marinushkin
2018-03-26 20:41 ` Andrew Chant
2018-03-26 21:13 ` Kirill Marinushkin [this message]
2018-03-26 21:44 ` Takashi Sakamoto
2018-03-26 21:53 ` Kirill Marinushkin
2018-03-27 19:12 ` Kirill Marinushkin
2018-03-26 8:19 ` Takashi Sakamoto
2018-03-26 18:37 ` Kirill Marinushkin
2018-03-26 18:42 ` Kirill Marinushkin
2018-03-26 22:03 ` Takashi Sakamoto
2018-03-26 22:22 ` Kirill Marinushkin
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=bb64a7f3-1664-65cc-871d-da7d5952a864@gmail.com \
--to=k.marinushkin@gmail.com \
--cc=achant@google.com \
--cc=alsa-devel@alsa-project.org \
--cc=o-takashi@sakamocchi.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.