All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Le Tan <tamlokveer@gmail.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Jan Kiszka" <jan.kiszka@web.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-trivial] [PATCH 2/2] block: replace fprintf(stderr, ...) with error_report()
Date: Sat, 24 May 2014 10:08:01 +0400	[thread overview]
Message-ID: <53803741.8050801@msgid.tls.msk.ru> (raw)
In-Reply-To: <CACrq+iK9+ARbYgkXeAFfdeLMmjb+EE04skdVk-POTyUSgY+xmw@mail.gmail.com>

24.05.2014 10:01, Le Tan пишет:
> I will fix the whitespace issues and resend this series with a new
> version later.

Please note, once again: I applied (with fixups) other 3 your patches,
so there's no need to resend those 3.

This one, besides a whitespace problem, needs an ACK from block subsystem
maintainers, because it touches too much code there.

Thanks,

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Le Tan <tamlokveer@gmail.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Jan Kiszka" <jan.kiszka@web.de>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH 2/2] block: replace fprintf(stderr, ...) with error_report()
Date: Sat, 24 May 2014 10:08:01 +0400	[thread overview]
Message-ID: <53803741.8050801@msgid.tls.msk.ru> (raw)
In-Reply-To: <CACrq+iK9+ARbYgkXeAFfdeLMmjb+EE04skdVk-POTyUSgY+xmw@mail.gmail.com>

24.05.2014 10:01, Le Tan пишет:
> I will fix the whitespace issues and resend this series with a new
> version later.

Please note, once again: I applied (with fixups) other 3 your patches,
so there's no need to resend those 3.

This one, besides a whitespace problem, needs an ACK from block subsystem
maintainers, because it touches too much code there.

Thanks,

/mjt

  reply	other threads:[~2014-05-24  6:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21  0:10 [Qemu-trivial] [PATCH 0/2] replace some fprintf(stderr, ...) with error_report() Le Tan
2014-05-21  0:10 ` [Qemu-devel] " Le Tan
2014-05-21  0:10 ` [Qemu-trivial] [PATCH 1/2] arch_init: replace " Le Tan
2014-05-21  0:10   ` [Qemu-devel] " Le Tan
2014-05-21  8:06   ` [Qemu-trivial] " Andreas Färber
2014-05-21  8:06     ` Andreas Färber
2014-05-23 20:11   ` [Qemu-trivial] " Michael Tokarev
2014-05-23 20:11     ` [Qemu-devel] " Michael Tokarev
2014-05-21  0:10 ` [Qemu-trivial] [PATCH 2/2] block: " Le Tan
2014-05-21  0:10   ` [Qemu-devel] " Le Tan
2014-05-23 20:27   ` [Qemu-trivial] " Michael Tokarev
2014-05-23 20:27     ` [Qemu-devel] " Michael Tokarev
2014-05-24  6:01     ` Le Tan
2014-05-24  6:01       ` [Qemu-devel] " Le Tan
2014-05-24  6:08       ` Michael Tokarev [this message]
2014-05-24  6:08         ` Michael Tokarev

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=53803741.8050801@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=afaerber@suse.de \
    --cc=jan.kiszka@web.de \
    --cc=kwolf@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=tamlokveer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.