From: Noah Goldstein <goldstein.w.n@gmail.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org, hjl.tools@gmail.com
Subject: Re: x86: Don't check PREFETCHWT1 in tst-cpu-features-cpuinfo.c
Date: Fri, 10 Mar 2023 01:04:19 -0600 [thread overview]
Message-ID: <CAFUsyf+wg-VaHAzt9Hhmgcjmbvh7nKUVsLoYDJBtxFJcjB=jXg@mail.gmail.com> (raw)
In-Reply-To: <xno7p142f2.fsf@greed.delorie.com>
On Thu, Mar 9, 2023 at 11:10 PM DJ Delorie <dj@redhat.com> wrote:
>
> Noah Goldstein <goldstein.w.n@gmail.com> writes:
> > Does platform/x86.h need to be updated as well? Although that might be harder
> > to change as its user facing.
>
> I'm not taking support for that bit out of glibc, just tweaking the
> consistency check to not care that the kernel doesn't report it in
> /proc/cpuinfo yet.
>
Oh, woops, I misread the patch.
next prev parent reply other threads:[~2023-03-10 7:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 3:43 DJ Delorie
2023-03-10 5:01 ` Noah Goldstein
2023-03-10 5:10 ` DJ Delorie
2023-03-10 7:04 ` Noah Goldstein [this message]
2023-03-10 7:04 ` Noah Goldstein
2023-03-20 19:01 ` DJ Delorie
2023-03-21 18:01 ` Noah Goldstein
2023-03-22 0:08 ` DJ Delorie
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='CAFUsyf+wg-VaHAzt9Hhmgcjmbvh7nKUVsLoYDJBtxFJcjB=jXg@mail.gmail.com' \
--to=goldstein.w.n@gmail.com \
--cc=dj@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).