From: "Emilio G. Cota" <cota@braap.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [Qemu-devel] Call for patches for the qemu-trivial pull request
Date: Thu, 25 Oct 2018 14:31:35 -0400 [thread overview]
Message-ID: <20181025183135.GA29428@flamenco> (raw)
In-Reply-To: <38b0df70-338e-c842-95bb-c1a5fbd54b7b@vivier.eu>
On Tue, Oct 23, 2018 at 11:04:36 +0100, Laurent Vivier wrote:
> So, it would be helpful if any of you knowing that some patches have to
> be added to the pull request send me their list.
I sent this one in August:
linux-user: fix comment s/atomic_write/atomic_set/
https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg01964.html
Thanks,
Emilio
next prev parent reply other threads:[~2018-10-25 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 10:04 [Qemu-devel] Call for patches for the qemu-trivial pull request Laurent Vivier
2018-10-25 6:56 ` Thomas Huth
2018-10-25 11:23 ` Laurent Vivier
2018-10-25 18:31 ` Emilio G. Cota [this message]
2018-10-25 20:13 ` Thomas Huth
2018-10-25 21:26 ` 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=20181025183135.GA29428@flamenco \
--to=cota@braap.org \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).