public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29622] Open file permission error under aarch64 architecture
Date: Tue, 18 Apr 2023 12:03:46 +0000	[thread overview]
Message-ID: <bug-29622-131-EvzjYqB0Gj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29622-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29622

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTABUG
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg
             Status|WAITING                     |RESOLVED

--- Comment #5 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
As per comment #1.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2023-04-18 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28  2:01 [Bug libc/29622] New: " dluyaning at gmail dot com
2022-09-28  2:02 ` [Bug libc/29622] " dluyaning at gmail dot com
2022-09-28  2:37 ` dluyaning at gmail dot com
2022-09-28  8:30 ` schwab@linux-m68k.org
2022-09-28  9:45 ` dluyaning at gmail dot com
2022-09-28  9:56 ` schwab@linux-m68k.org
2022-09-29  2:47 ` dluyaning at gmail dot com
2023-04-18 12:03 ` adhemerval.zanella at linaro dot org [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-29622-131-EvzjYqB0Gj@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).