All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-trivial] [Qemu-devel] Ping http://patchwork.ozlabs.org/patch/251410/
Date: Sat, 14 Sep 2013 13:08:11 +0400	[thread overview]
Message-ID: <5234277B.9030809@msgid.tls.msk.ru> (raw)
In-Reply-To: <20130912085155.GH1965@stefanha-thinkpad.redhat.com>

12.09.2013 12:51, Stefan Hajnoczi пишет:
> On Wed, Sep 11, 2013 at 04:08:01PM -0700, Richard Henderson wrote:
>> There have been two patches posted for this uninitialized warning, outstanding
>> since June 14.  I still encounter this daily...
>
> I'm still happy with the patch.
>
> Michael: Do you want to take this through the trivial patches tree?

Yes it looks like a trivial patch, but it has at least 2 issues:

  1) it does 2 different things in one patch
    (one for vscclient and one for iov)

  2) the subject line is too generic.

On the other hand, asking for a V4 for such a trivial thing is a bit
too much, in my opinion.

So - since by applying to -trivial I'm adding my S-o-b anyway - I'll
split it into two patches and fix $subject.

Thanks, applied to the trivial-patches queue.

/mjt


WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-trivial@nongnu.org, Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [Qemu-trivial] Ping http://patchwork.ozlabs.org/patch/251410/
Date: Sat, 14 Sep 2013 13:08:11 +0400	[thread overview]
Message-ID: <5234277B.9030809@msgid.tls.msk.ru> (raw)
In-Reply-To: <20130912085155.GH1965@stefanha-thinkpad.redhat.com>

12.09.2013 12:51, Stefan Hajnoczi пишет:
> On Wed, Sep 11, 2013 at 04:08:01PM -0700, Richard Henderson wrote:
>> There have been two patches posted for this uninitialized warning, outstanding
>> since June 14.  I still encounter this daily...
>
> I'm still happy with the patch.
>
> Michael: Do you want to take this through the trivial patches tree?

Yes it looks like a trivial patch, but it has at least 2 issues:

  1) it does 2 different things in one patch
    (one for vscclient and one for iov)

  2) the subject line is too generic.

On the other hand, asking for a V4 for such a trivial thing is a bit
too much, in my opinion.

So - since by applying to -trivial I'm adding my S-o-b anyway - I'll
split it into two patches and fix $subject.

Thanks, applied to the trivial-patches queue.

/mjt

  reply	other threads:[~2013-09-14  9:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 23:08 [Qemu-devel] Ping http://patchwork.ozlabs.org/patch/251410/ Richard Henderson
2013-09-12  8:49 ` [Qemu-trivial] " Peter Maydell
2013-09-12  8:49   ` Peter Maydell
2013-09-12  8:51 ` [Qemu-trivial] " Stefan Hajnoczi
2013-09-12  8:51   ` Stefan Hajnoczi
2013-09-14  9:08   ` Michael Tokarev [this message]
2013-09-14  9:08     ` [Qemu-devel] [Qemu-trivial] " 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=5234277B.9030809@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.com \
    --cc=xiawenc@linux.vnet.ibm.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.