From: Andreas Schwab <schwab@suse.de>
To: Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: implement renameat2
Date: Tue, 23 Jan 2018 11:26:04 +0100 [thread overview]
Message-ID: <mvminbsub0j.fsf@suse.de> (raw)
In-Reply-To: <40b82ee1-416b-20c6-4745-218d8e3cdd24@vivier.eu> (Laurent Vivier's message of "Tue, 23 Jan 2018 01:37:58 +0100")
On Jan 23 2018, Laurent Vivier <laurent@vivier.eu> wrote:
> And, please, test it (build/run).
This was tested by bootstrapping openSUSE Factory for RISC-V.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2018-01-23 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 17:44 [Qemu-devel] [PATCH] linux-user: implement renameat2 Andreas Schwab
2018-01-22 17:48 ` no-reply
2018-01-23 0:35 ` Laurent Vivier
2018-01-23 10:22 ` Andreas Schwab
2018-01-23 0:37 ` Laurent Vivier
2018-01-23 10:26 ` Andreas Schwab [this message]
2018-01-23 10:53 ` Laurent Vivier
2018-01-23 10:53 ` [Qemu-devel] [PATCH v2] " Andreas Schwab
2018-01-23 11:20 ` 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=mvminbsub0j.fsf@suse.de \
--to=schwab@suse.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).