Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Vitalii Torshyn <vitaly.torshyn@gmail.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org, luke@ljones.dev
Subject: Re: [PATCH] sound, hda/realtek: Fixes for Asus GU605M and GA403U sound
Date: Thu, 18 Apr 2024 08:47:01 +0200	[thread overview]
Message-ID: <87frvjxj4q.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240411125803.18539-1-vitaly.torshyn@gmail.com>

On Thu, 11 Apr 2024 14:58:03 +0200,
Vitalii Torshyn wrote:
> 
> Added the correct pin table for Asus GU605M and GA403U, enabling all
> speakers to be controlled with the master.
> Updated quirks for GU605M and GA403U by including the pin table patch
> in the chain.
> 
> Signed-off-by: Luke D. Jones <luke@ljones.dev>
> Signed-off-by: Vitalii Torshyn <vitaly.torshyn@gmail.com>

Applied now to for-linus branch.  Thanks.


Takashi

      parent reply	other threads:[~2024-04-18  6:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11 12:58 [PATCH] sound, hda/realtek: Fixes for Asus GU605M and GA403U sound Vitalii Torshyn
2024-04-13 20:31 ` Luke Jones
2024-04-18  6:47 ` Takashi Iwai [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=87frvjxj4q.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-sound@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=tiwai@suse.com \
    --cc=vitaly.torshyn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox