From: Stefan Liebler <stli@linux.ibm.com>
To: Zack Weinberg <zackw@panix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
"Carlos O'Donell" <carlos@redhat.com>
Subject: Re: Fix string/tst-xbzero-opt if build with gcc head.
Date: Mon, 23 Jul 2018 06:42:00 -0000 [thread overview]
Message-ID: <3cd17f42-73af-fa12-9f85-5fa3c515f05a@linux.ibm.com> (raw)
In-Reply-To: <CAKCAbMgop4GAGWa4Kb7+G6zyrKQdJqOmATaYeuixgLJEUGwmTA@mail.gmail.com>
On 07/16/2018 03:18 PM, Zack Weinberg wrote:
> On Mon, Jul 16, 2018 at 9:13 AM, Stefan Liebler <stli@linux.ibm.com> wrote:
>> On 07/16/2018 02:36 PM, Zack Weinberg wrote:
>>> On Mon, Jul 16, 2018 at 7:05 AM, Stefan Liebler <stli@linux.ibm.com>
>>> wrote:
>>>> Okay. Then here is a new version of the patch without the empty asm.
>>>> If build with GCC head on s390x, setup_no_clear is now filling the buffer
>>>> and setup_ordinary_clear is just a tail call to setup_no_clear (same
>>>> behaviour as before).
>>>
>>>
>>> Yes, this change is OK.
>>
>> Okay. Thank you.
>> Shall I commit this test-fix before or after the release?
>
> Carlos has the last word but we usually accept bugfixes to test cases
> right up till the hard freeze.
>
> zw
>
Carlos,
what about this bugfix for this test?
Can I commit it now or shall I wait commit it after the release?
Bye
Stefan
next prev parent reply other threads:[~2018-07-23 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 14:22 Stefan Liebler
2018-07-12 16:42 ` Zack Weinberg
2018-07-16 11:05 ` Stefan Liebler
2018-07-16 12:36 ` Zack Weinberg
2018-07-16 13:13 ` Stefan Liebler
2018-07-16 13:18 ` Zack Weinberg
2018-07-23 6:42 ` Stefan Liebler [this message]
2018-07-26 13:33 ` Carlos O'Donell
2018-07-26 15:13 ` [COMMITTED] " Stefan Liebler
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=3cd17f42-73af-fa12-9f85-5fa3c515f05a@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).