From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qinghao Tang <luodalongde@gmail.com>,
qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] scsi: initialise info object with appropriate size
Date: Mon, 21 Dec 2015 17:39:47 +0100 [thread overview]
Message-ID: <56782B53.7000308@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1512212158450.26574@wniryva>
On 21/12/2015 17:33, P J P wrote:
> | Yes, it is. I've queued this patch to my for-2.6 branch.
>
> Okay, cool! Should I separately send it for 2.5 at qemu-stable?
I can add the Cc to the commit message as well. For now it's enough to
send a message in Cc so that the qemu-stable people notice it.
Paolo
next prev parent reply other threads:[~2015-12-21 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 9:43 [Qemu-devel] [PATCH] scsi: initialise info object with appropriate size P J P
2015-12-21 15:29 ` Paolo Bonzini
2015-12-21 16:33 ` P J P
2015-12-21 16:39 ` Paolo Bonzini [this message]
2015-12-21 17:56 ` P J P
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=56782B53.7000308@redhat.com \
--to=pbonzini@redhat.com \
--cc=luodalongde@gmail.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).