public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Luke D. Jones" <luke@ljones.dev>
Cc: tiwai@suse.com, linux-kernel@vger.kernel.org,
	alsa-devel@alsa-project.org, perex@perex.cz
Subject: Re: [PATCH v2 0/3] sound: realtek: add quirks for ASUS G513, G533Z, GA503R
Date: Thu, 15 Sep 2022 17:56:41 +0200	[thread overview]
Message-ID: <87fsgsvdfq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220915080921.35563-1-luke@ljones.dev>

On Thu, 15 Sep 2022 10:09:18 +0200,
Luke D. Jones wrote:
> 
> This series adds quirks to fix pincfg for the ASUS ROG G513 and G533Z laptops, and adds a mapping
> for the ASUS ROG GA503R to use the previous G15/G14 quirks which fix the DAC mapping.
> 
> Changelog:
> V2:
> - Use smallcaps in hex string
> - Chain the G533Z quirk with the G513 quirk as they use the same base pincfg
> - Add the quirk for GA503R series to use GA401 quirk
> 
> Luke D. Jones (3):
>   sound: realtek: Add pincfg for ASUS G513 HP jack
>   sound: realtek: Add pincfg for ASUS G533Z HP jack
>   sound: realtek: Add quirk for ASUS GA503R laptop

Now applied all patches, but I corrected the positions of the new
entries to be in the SSID order locally.  Also, the subject lines are
adjusted to "ALSA:" prefix.


thanks,

Takashi

  parent reply	other threads:[~2022-09-15 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  8:09 [PATCH v2 0/3] sound: realtek: add quirks for ASUS G513, G533Z, GA503R Luke D. Jones
2022-09-15  8:09 ` [PATCH v2 1/3] sound: realtek: Add pincfg for ASUS G513 HP jack Luke D. Jones
2022-09-15  8:09 ` [PATCH v2 2/3] sound: realtek: Add pincfg for ASUS G533Z " Luke D. Jones
2022-09-15  8:09 ` [PATCH v2 3/3] sound: realtek: Add quirk for ASUS GA503R laptop Luke D. Jones
2022-09-15 15:56 ` Takashi Iwai [this message]
2022-09-16  8:46   ` [PATCH v2 0/3] sound: realtek: add quirks for ASUS G513, G533Z, GA503R Luke Jones
2022-09-18 22:18   ` Luke Jones

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=87fsgsvdfq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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