From: Riku Voipio <riku.voipio@iki.fi>
To: Zach Riggle <zachriggle@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eric Blake <eblake@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
Laurent Vivier <laurent@vivier.eu>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] linux-user: fix is_proc_myself to check the paths via realpath
Date: Tue, 7 Nov 2017 20:06:34 +0000 [thread overview]
Message-ID: <20171107200634.GB27631@kos.to> (raw)
In-Reply-To: <CAMP9c5krrvH-TpH0mM1D3Fm8=E+C7nYHU8h3b5CwU1Nb2HxN-A@mail.gmail.com>
Hi,
On Mon, Nov 06, 2017 at 08:17:44PM +0000, Zach Riggle wrote:
> Ping! What needs to be done to move this forward? My current implementation
> is compatible with musl.
I'll have a look at it soon.
Riku
> On Thu, Nov 2, 2017 at 12:36 PM Peter Maydell <peter.maydell@linaro.org>
> wrote:
>
> > On 28 October 2017 at 06:14, Eric Blake <eblake@redhat.com> wrote:
> > > By definition, in linux-user, we ARE using glibc; therefore, you are
> > > free to use all GNU extensions.
> >
> > Don't we also support musl libc? I forget...
> >
> > thanks
> > -- PMM
> >
next prev parent reply other threads:[~2017-11-07 20:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 23:07 [Qemu-devel] [PATCH] linux-user: fix is_proc_myself to check the paths via realpath Zach Riggle
2017-10-25 2:55 ` no-reply
2017-10-25 3:34 ` [Qemu-devel] [PATCH v2] " Zach Riggle
2017-10-26 21:06 ` Zach Riggle
2017-10-27 9:36 ` Riku Voipio
2017-10-27 17:05 ` Zach Riggle
2017-10-27 19:07 ` Zach Riggle
2017-10-28 5:14 ` Eric Blake
2017-11-02 18:26 ` Zach Riggle
2017-11-02 19:35 ` Peter Maydell
2017-11-06 20:17 ` Zach Riggle
2017-11-07 20:06 ` Riku Voipio [this message]
2017-11-10 21:44 ` Zach Riggle
2017-11-10 23:44 ` Laurent Vivier
2017-11-11 1:47 ` Zach Riggle
2017-11-11 1:48 ` Zach Riggle
2017-11-14 19:44 ` Laurent Vivier
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=20171107200634.GB27631@kos.to \
--to=riku.voipio@iki.fi \
--cc=eblake@redhat.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zachriggle@gmail.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 NNTP newsgroup(s).