From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andy Chi <andy.chi@canonical.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Stefan Binding <sbinding@opensource.cirrus.com>,
Kailang Yang <kailang@realtek.com>,
"Luke D. Jones" <luke@ljones.dev>,
Shenghao Ding <shenghao-ding@ti.com>,
Matthew Anderson <ruinairas1992@gmail.com>,
Luka Guzenko <l.guzenko@web.de>,
Yuchi Yang <yangyuchi66@gmail.com>,
Vitaly Rodionov <vitalyr@opensource.cirrus.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook
Date: Tue, 2 Jan 2024 19:08:45 -0300 [thread overview]
Message-ID: <ZZSJbWB2O7mKVbeW@geday> (raw)
In-Reply-To: <87y1d77pg4.wl-tiwai@suse.de>
On Tue, Jan 02, 2024 at 03:57:47PM +0100, Takashi Iwai wrote:
> I merged as is now with some comments about the new model.
> It's fine with the current patch if the entry will be updated later
> with a proper model name; having the code fix before the name
> definition would be more important.
Thanks Takashi, actually it's a commit from the ideal world. I wish more
integrators would work together with Linux companies to launch new
products that work smoothly, like we see here.
I appreciate you adding the note about it being a new model without a
proper name. It's a middle path that doesn't overwork you and Andy, and
my concern is still addressed that way.
Regards,
Geraldo Nascimento
>
>
> thanks,
>
> Takashi
prev parent reply other threads:[~2024-01-02 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 2:49 [PATCH] ALSA: hda/realtek: fix mute/micmute LEDs for a HP ZBook Andy Chi
2024-01-02 4:26 ` Geraldo Nascimento
[not found] ` <CAEzXkg3YiH_XQGz4vbFc7dptmMSWrVDrALdNJAmmQgWa17PP1A@mail.gmail.com>
2024-01-02 5:49 ` Andy Chi
2024-01-02 6:42 ` Geraldo Nascimento
2024-01-02 6:59 ` Andy Chi
2024-01-02 7:45 ` Geraldo Nascimento
2024-01-02 14:57 ` Takashi Iwai
2024-01-02 22:08 ` Geraldo Nascimento [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=ZZSJbWB2O7mKVbeW@geday \
--to=geraldogabriel@gmail.com \
--cc=andy.chi@canonical.com \
--cc=kailang@realtek.com \
--cc=l.guzenko@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=perex@perex.cz \
--cc=ruinairas1992@gmail.com \
--cc=sbinding@opensource.cirrus.com \
--cc=shenghao-ding@ti.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=vitalyr@opensource.cirrus.com \
--cc=yangyuchi66@gmail.com \
/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.