From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Joe Ramsay <Joe.Ramsay@arm.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/2] benchtests: Move libmvec benchtest inputs to benchtests directory
Date: Mon, 27 Mar 2023 14:36:30 +0100 [thread overview]
Message-ID: <ZCGb3tGLjggU6bis@arm.com> (raw)
In-Reply-To: <20230324121011.629-1-Joe.Ramsay@arm.com>
The 03/24/2023 12:10, Joe Ramsay via Libc-alpha wrote:
> This allows other targets to use the same inputs for their own libmvec
> microbenchmarks without having to duplicate them in their own
> subdirectory.
This looks good to commit, if you don't have commit rights
then let me know and i'll commit it for you.
thanks.
Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
prev parent reply other threads:[~2023-03-27 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 12:10 Joe Ramsay
2023-03-24 12:10 ` [PATCH 2/2] Enable libmvec support for AArch64 Joe Ramsay
2023-04-06 16:26 ` Szabolcs Nagy
2023-03-27 13:36 ` Szabolcs Nagy [this message]
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=ZCGb3tGLjggU6bis@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Joe.Ramsay@arm.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).