Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/6] Revert "ALSA: hda/hdmi: add connect-all quirk for ASUSTeK Prime B560M-A"
Date: Mon, 18 Dec 2023 18:18:14 +0200	[thread overview]
Message-ID: <87frzzv60p.fsf@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2312181540440.14041@eliteleevi.tm.intel.com>

On Mon, 18 Dec 2023, Kai Vehmanen <kai.vehmanen@linux.intel.com> wrote:
> Hi,
>
> On Mon, 18 Dec 2023, Jani Nikula wrote:
>
>> On Tue, 12 Dec 2023, Kai Vehmanen <kai.vehmanen@linux.intel.com> wrote:
>> > --- a/sound/pci/hda/patch_hdmi.c
>> > +++ b/sound/pci/hda/patch_hdmi.c
>> > @@ -1993,7 +1993,6 @@ static const struct snd_pci_quirk force_connect_list[] = {
>> >  	SND_PCI_QUIRK(0x103c, 0x871a, "HP", 1),
>> >  	SND_PCI_QUIRK(0x103c, 0x8711, "HP", 1),
>> >  	SND_PCI_QUIRK(0x103c, 0x8715, "HP", 1),
>> > -	SND_PCI_QUIRK(0x1043, 0x8694, "ASUS", 1),  /* SKL/KBL + PRIME B560M-A */
>> 
>> So there's no replacement for this commit. Is that correct?
>> 
>> I've rebased topic/core-for-CI on top of v6.7-rc6, and everything else
>> got resolved with the upstream commits but this. I left this one in for
>> now, should I drop it?
>
> yes, this can be dropped. This was reported in the bug report as one 
> affected id, but it's not valid and I dropped in the series I sent 
> upstream. The i915 CI had no failures with this dropped, so seems we are 
> good to go.

Thanks, done.

BR,
Jani.

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-12-18 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 18:02 [PATCH 0/6] ALSA: hda/hdmi: align force-connect quirks with upstream Kai Vehmanen
2023-12-12 18:02 ` [PATCH 1/6] Revert "ALSA: hda/hdmi: add force-connect quirk for ASUSTeK Z170M Pro" Kai Vehmanen
2023-12-12 18:02 ` [PATCH 2/6] Revert "ALSA: hda/hdmi: add connect-all quirk for ASUSTeK Z170 Pro" Kai Vehmanen
2023-12-12 18:02 ` [PATCH 3/6] Revert "ALSA: hda/hdmi: add connect-all quirk for ASUSTeK Prime B560M-A" Kai Vehmanen
2023-12-18 12:44   ` Jani Nikula
2023-12-18 13:43     ` Kai Vehmanen
2023-12-18 16:18       ` Jani Nikula [this message]
2023-12-12 18:02 ` [PATCH 4/6] Revert "ALSA: hda/hdmi: add connect-all quirk for NUC5CPYB" Kai Vehmanen
2023-12-12 18:02 ` [PATCH 5/6] ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants Kai Vehmanen
2023-12-12 18:02 ` [PATCH 6/6] ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB Kai Vehmanen
2023-12-12 19:50 ` ✗ Fi.CI.BAT: failure for ALSA: hda/hdmi: align force-connect quirks with upstream Patchwork

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=87frzzv60p.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.vehmanen@linux.intel.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