From: Paolo Bonzini <pbonzini@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH][v8] megasas: LSI Megaraid SAS HBA emulation
Date: Fri, 13 Jan 2012 11:14:17 +0100 [thread overview]
Message-ID: <4F1003F9.4020309@redhat.com> (raw)
In-Reply-To: <4F0FFD91.6010603@suse.de>
On 01/13/2012 10:46 AM, Hannes Reinecke wrote:
> So, I should be removing the 'disable' keyword, then, correct?
Yes.
> The strings are just there to avoid trace statement duplication. But
> if that's not a problem then I can easily convert the strings to
> individual trace statements.
No, don't bother.
Paolo
prev parent reply other threads:[~2012-01-13 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 10:43 [Qemu-devel] [PATCH][v8] megasas: LSI Megaraid SAS HBA emulation Hannes Reinecke
2012-01-12 14:45 ` Paolo Bonzini
2012-01-12 18:04 ` Stefan Hajnoczi
2012-01-13 9:46 ` Hannes Reinecke
2012-01-13 10:14 ` Paolo Bonzini [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=4F1003F9.4020309@redhat.com \
--to=pbonzini@redhat.com \
--cc=hare@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 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).