All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Greg Kurz <gkurz@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] 9pfs: fsdev: use error_report() instead of fprintf(stderr)
Date: Tue, 19 Jan 2016 13:19:31 +0100	[thread overview]
Message-ID: <87wpr5ep7w.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20160119122837.32bb9840@bahia.huguette.org> (Greg Kurz's message of "Tue, 19 Jan 2016 12:28:37 +0100")

Greg Kurz <gkurz@linux.vnet.ibm.com> writes:

> On Mon, 18 Jan 2016 17:39:28 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
>
>> Greg Kurz <gkurz@linux.vnet.ibm.com> writes:
>> 
>> > 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 ?  
>> 
>> It can certainly go through your tree!
>> 
>> My tree is meant for crosscutting error work.  I also offer it
>> maintainers who prefer to leave the pull request to me.
>> 
>> PATCH 1 could use a bit of polish, and I encourage you to respin.  But
>> it's not wrong, therefore
>> 
>> Series
>> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>> 
>
> Thanks Markus !
>
> I've respun the series with your suggestions. Is it expected I repost to
> qemu-devel before doing a pull request ?

Maintainers sometimes skip posting trivially revised patches for
additional review before doing a pull request.  Posting them is never
wrong, though.

When in doubt, post :)

      reply	other threads:[~2016-01-19 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18 15:02 [Qemu-devel] [PATCH 0/2] 9pfs: fsdev: use error_report() instead of fprintf(stderr) Greg Kurz
2016-01-18 15:02 ` [Qemu-devel] [PATCH 1/2] 9pfs: " 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 [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=87wpr5ep7w.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gkurz@linux.vnet.ibm.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 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.