public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26338] io/tst-copy_file_range may incorrectly detect availability of copy_file_range file system support
Date: Fri, 07 Aug 2020 10:07:00 +0000 [thread overview]
Message-ID: <bug-26338-131-m2zWuGD9XV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26338-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26338
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|io/tst-copy_file_range |io/tst-copy_file_range may
|fails on RHEL 7.8 hosts |incorrectly detect
| |availability of
| |copy_file_range file system
| |support
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2020-08-07 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-05 11:47 [Bug build/26338] New: io/tst-copy_file_range fails on RHEL 7.8 hosts romain.geissler at amadeus dot com
2020-08-05 12:42 ` [Bug build/26338] " adhemerval.zanella at linaro dot org
2020-08-05 13:24 ` carlos at redhat dot com
2020-08-05 13:38 ` fweimer at redhat dot com
2020-08-05 14:01 ` adhemerval.zanella at linaro dot org
2020-08-05 14:08 ` fweimer at redhat dot com
2020-08-05 14:20 ` adhemerval.zanella at linaro dot org
2020-08-05 14:25 ` fweimer at redhat dot com
2020-08-05 14:28 ` adhemerval.zanella at linaro dot org
2020-08-07 9:56 ` romain.geissler at amadeus dot com
2020-08-07 10:06 ` fweimer at redhat dot com
2020-08-07 10:07 ` fweimer at redhat dot com [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=bug-26338-131-m2zWuGD9XV@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).