Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Anisse Astier <anisse@astier.eu>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] hda_analyzer: don't fail to display audio selector if caps variables aren't available
Date: Thu, 30 May 2013 14:37:58 +0200	[thread overview]
Message-ID: <20130530143758.0c174743@serenity> (raw)
In-Reply-To: <51A745A7.5020403@perex.cz>

On Thu, 30 May 2013 14:27:19 +0200, Jaroslav Kysela <perex@perex.cz> wrote :

> Date 30.5.2013 14:14, Anisse Astier wrote:
> > In particular, when an audio selector node has Amp-In caps: N/A, it
> > allows to still interact with the selector, and not have TypeError traceback
> > throwns because of NoneType variables.
> 
> When ofs is None, the steps are not defined, too. I fixed it in:
> 
> http://git.alsa-project.org/?p=alsa.git;a=commitdiff;h=5bcf62d6947fe348a2b055bce633df1d12ff4370
> 

Awesome, thanks.

Anisse

      reply	other threads:[~2013-05-30 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 12:14 [PATCH] hda_analyzer: don't fail to display audio selector if caps variables aren't available Anisse Astier
2013-05-30 12:27 ` Jaroslav Kysela
2013-05-30 12:37   ` Anisse Astier [this message]

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=20130530143758.0c174743@serenity \
    --to=anisse@astier.eu \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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