From: Joe Perches <joe@perches.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 4.19-rc1
Date: Wed, 15 Aug 2018 19:05:25 -0700 [thread overview]
Message-ID: <fb8d7d867726b934650ed20ceb4fe0d2a6a4f0f9.camel@perches.com> (raw)
In-Reply-To: <CA+55aFxZDYTFKM4-e89_2SKHjHh_8RCZe7whKa2kCWRFk4mAdg@mail.gmail.com>
On Wed, 2018-08-15 at 19:00 -0700, Linus Torvalds wrote:
> On Wed, Aug 15, 2018 at 6:27 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > I have no idea _why_, but it's consistent, and it bisects down to
> >
> > c647f806b8c2 "ALSA: hda - Allow multiple ADCs for mic mute LED controls"
> >
> > where the previous commit works fine, but that commit definitely
> > causes the problem.
>
> Hmm.
>
> That commit changes the return value of the
> snd_hda_gen_add_micmute_led(), but doesn't change any of the callers.
>
> Now, almost no caller actually checks the return value.
>
> Almost.
>
> There is *one* caller that does, though:
>
> sound/pci/hda/dell_wmi_helper.c:
> alc_fixup_dell_wmi()
>
> And yes, the laptop that breaks is a Dell. An XPS13.
>
> I bet that instead of reverting, I can just change that
>
> (snd_hda_gen_add_micmute_led(codec,
> dell_micmute_update) <= 0);
>
> to test for "< 0" instead of "<= 0".
Why does the commit change snd_hda_gen_add_micmute_led
to return 0; instead of return 1;
That bit looks wrong.
next prev parent reply other threads:[~2018-08-16 2:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 12:34 Takashi Iwai
2018-08-15 22:47 ` Linus Torvalds
2018-08-16 1:27 ` Linus Torvalds
2018-08-16 1:48 ` Linus Torvalds
2018-08-16 2:00 ` Linus Torvalds
2018-08-16 2:05 ` Joe Perches [this message]
2018-08-16 2:08 ` Linus Torvalds
2018-08-16 5:29 ` 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=fb8d7d867726b934650ed20ceb4fe0d2a6a4f0f9.camel@perches.com \
--to=joe@perches.com \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®