qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Greg Kurz <gkurz@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 0/2] 9pfs: fsdev: use error_report() instead of fprintf(stderr)
Date: Mon, 18 Jan 2016 16:02:34 +0100	[thread overview]
Message-ID: <20160118150234.30699.57180.stgit@bahia.huguette.org> (raw)

Hi,

This series moves all the 9pfs/fsdev code to use error_report(), with the
notable exception of virtfs-proxy-helper, which doesn't need it.

Markus,

Should this patches go through your tree ? Or can they go through my 9p tree
if you ack them ?

Cheers.

--
Greg

---

Greg Kurz (2):
      9pfs: use error_report() instead of fprintf(stderr)
      fsdev: use error_report() instead of fprintf(stderr)


 fsdev/qemu-fsdev.c  |    7 ++++---
 hw/9pfs/9p-handle.c |    5 +++--
 hw/9pfs/9p-local.c  |   15 ++++++++-------
 hw/9pfs/9p-proxy.c  |   12 ++++++------
 hw/9pfs/9p.c        |    2 +-
 5 files changed, 22 insertions(+), 19 deletions(-)

             reply	other threads:[~2016-01-18 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 15:02 Greg Kurz [this message]
2016-01-18 15:02 ` [Qemu-devel] [PATCH 1/2] 9pfs: use error_report() instead of fprintf(stderr) Greg Kurz
2016-01-18 16:35   ` Markus Armbruster
2016-01-19 11:25     ` Greg Kurz
2016-01-18 15:02 ` [Qemu-devel] [PATCH 2/2] fsdev: " Greg Kurz
2016-01-18 16:39 ` [Qemu-devel] [PATCH 0/2] 9pfs: " Markus Armbruster
2016-01-19 11:28   ` Greg Kurz
2016-01-19 12:19     ` Markus Armbruster

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=20160118150234.30699.57180.stgit@bahia.huguette.org \
    --to=gkurz@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --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).