From: "Krzysztof Wilczyński" <kw@linux.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: x86@kernel.org, jose.souza@intel.com, hpa@zytor.com,
bp@alien8.de, mingo@redhat.com, tglx@linutronix.de,
kai.heng.feng@canonical.com, bhelgaas@google.com,
linux-pci@vger.kernel.org, rudolph@fb.com, xapienz@fb.com,
bmilton@fb.com, stable@vger.kernel.org
Subject: Re: [PATCH] x86/intel: Disable HPET on another Intel Coffee Lake platform
Date: Fri, 17 Sep 2021 16:00:03 +0200 [thread overview]
Message-ID: <20210917140003.GA1520823@rocinante> (raw)
In-Reply-To: <20210916131739.1260552-1-kuba@kernel.org>
Hi Jakub,
[...]
> The Intel documentation does not list my device [1], but
> linuxhw [2] does, and it seems to list a few more bridges
> we do not currently cover (3e31, 3ecc, 3e35, 3e0f).
This might be out-of-scope for this particular patch, but it makes me
wonder - if we know that these other bridges were identified as having the
same issue, would it be prudent to add a quriks for them too? It might
save some people a headache and such.
Krzysztof
next prev parent reply other threads:[~2021-09-17 14:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 13:17 [PATCH] x86/intel: Disable HPET on another Intel Coffee Lake platform Jakub Kicinski
2021-09-16 15:07 ` Bjorn Helgaas
2021-09-16 15:30 ` Jakub Kicinski
2021-09-16 16:35 ` Paul E. McKenney
2021-09-17 2:57 ` Jakub Kicinski
2021-09-17 3:33 ` Paul E. McKenney
2021-09-17 9:11 ` Peter Zijlstra
2021-09-17 9:34 ` Peter Zijlstra
2021-09-19 0:14 ` Thomas Gleixner
2021-09-21 18:05 ` Rafael J. Wysocki
2021-09-21 20:18 ` Thomas Gleixner
2021-09-22 20:27 ` Rafael J. Wysocki
2021-09-22 22:21 ` Thomas Gleixner
2021-09-23 10:46 ` Rafael J. Wysocki
2021-09-17 14:00 ` Krzysztof Wilczyński [this message]
2021-09-17 14:58 ` Jakub Kicinski
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=20210917140003.GA1520823@rocinante \
--to=kw@linux.com \
--cc=bhelgaas@google.com \
--cc=bmilton@fb.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jose.souza@intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rudolph@fb.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xapienz@fb.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