From: "Emilio G. Cota" <cota@braap.org>
To: qemu-trivial@nongnu.org
Cc: qemu-devel@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: [Qemu-devel] [PATCH 0/4] Some trivial fixes, mostly comment typos
Date: Thu, 16 Nov 2017 15:04:03 -0500 [thread overview]
Message-ID: <20171116200403.GA9824@flamenco> (raw)
In-Reply-To: <1508364103-16131-1-git-send-email-cota@braap.org>
On Wed, Oct 18, 2017 at 18:01:39 -0400, Emilio G. Cota wrote:
> A few trivial fixes that I embedded in a previous (unrelated) patchset.
> Better to submit them separately as a standalone "trivial" patchset.
*ping*
Can someone please pick up patches 1, 3 and 4?
Thanks,
Emilio
prev parent reply other threads:[~2017-11-16 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 22:01 [Qemu-devel] [PATCH 0/4] Some trivial fixes, mostly comment typos Emilio G. Cota
2017-10-18 22:01 ` [Qemu-devel] [PATCH 1/4] disas/arm: fix 'instuction' typo in comment Emilio G. Cota
2017-10-18 22:01 ` [Qemu-devel] [PATCH 2/4] linux-user: fix 'finshed' " Emilio G. Cota
2017-11-06 20:04 ` Riku Voipio
2017-10-18 22:01 ` [Qemu-devel] [PATCH 3/4] translate-all: fix 'consisits' " Emilio G. Cota
2017-10-18 22:01 ` [Qemu-devel] [PATCH 4/4] qht: fix kernel-doc markup in qht.h Emilio G. Cota
2017-11-16 20:04 ` Emilio G. Cota [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=20171116200403.GA9824@flamenco \
--to=cota@braap.org \
--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).