From: Andreas Schwab <schwab@suse.de>
To: "Karumanchi, Sajan via Libc-alpha" <libc-alpha@sourceware.org>
Cc: Florian Weimer <fweimer@redhat.com>,
"carlos@redhat.com" <carlos@redhat.com>,
"Karumanchi, Sajan" <Sajan.Karumanchi@amd.com>,
"Mallappa, Premachandra" <Premachandra.Mallappa@amd.com>
Subject: Re: [PATCH v1] x86: Cache computation for AMD architecture.
Date: Thu, 09 Feb 2023 14:43:59 +0100 [thread overview]
Message-ID: <mvmbkm3uf6o.fsf@suse.de> (raw)
In-Reply-To: <SJ0PR12MB5633E54F23DE8980DCD6C4F089C79@SJ0PR12MB5633.namprd12.prod.outlook.com> (Sajan via Libc-alpha Karumanchi's message of "Wed, 18 Jan 2023 07:39:42 +0000")
On Jan 18 2023, Karumanchi, Sajan via Libc-alpha wrote:
> diff --git a/sysdeps/x86/dl-cacheinfo.h b/sysdeps/x86/dl-cacheinfo.h
> index e9f3382108..21ac0a2dad 100644
> --- a/sysdeps/x86/dl-cacheinfo.h
> +++ b/sysdeps/x86/dl-cacheinfo.h
> @@ -311,117 +311,47 @@ handle_intel (int name, const struct cpu_features *cpu_features)
>
>
> static long int __attribute__ ((noinline))
> -handle_amd (int name)
> +handle_amd (int name, const struct cpu_features *cpu_features)
Nothing uses that argument.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-02-09 13:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 11:53 [PATCH] " Karumanchi, Sajan
2023-01-16 12:33 ` Florian Weimer
2023-01-18 7:39 ` [PATCH v1] " Karumanchi, Sajan
2023-01-18 14:54 ` Florian Weimer
2023-01-18 15:59 ` Carlos O'Donell
2023-02-09 13:43 ` Andreas Schwab [this message]
2023-05-08 17:06 ` Florian Weimer
2023-05-11 7:15 ` Karumanchi, Sajan
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=mvmbkm3uf6o.fsf@suse.de \
--to=schwab@suse.de \
--cc=Premachandra.Mallappa@amd.com \
--cc=Sajan.Karumanchi@amd.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.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).