From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org, Peter Bergner <bergner@linux.ibm.com>
Subject: Re: [PATCH] benchtests: Improve benchtests for strstr
Date: Mon, 18 Mar 2024 09:53:19 -0300 [thread overview]
Message-ID: <961eac8d-6b59-436a-9042-1e360f92e0fb@linaro.org> (raw)
In-Reply-To: <mvmil1jk8v3.fsf@suse.de>
On 18/03/24 09:44, Andreas Schwab wrote:
>> Content-Type: text/plain; charset=yes
>
> yes is not a valid charset.
>
Hum, I am not sure why I getting this.
next prev parent reply other threads:[~2024-03-18 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 12:27 [PATCH] benchtests: Improve benchtests for strstr Adhemerval Zanella
2024-03-18 12:44 ` Andreas Schwab
2024-03-18 12:53 ` Adhemerval Zanella Netto [this message]
2024-03-18 13:05 ` Andreas Schwab
2024-03-18 13:28 ` Adhemerval Zanella Netto
2024-03-18 19:33 ` Noah Goldstein
2024-03-27 15:35 ` Arjun Shankar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=961eac8d-6b59-436a-9042-1e360f92e0fb@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=bergner@linux.ibm.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).