From: Paolo Bonzini <pbonzini@redhat.com>
To: P J P <ppandit@redhat.com>, Qemu Developers <qemu-devel@nongnu.org>
Cc: Li Qiang <liqiang6-s@360.cn>, Hannes Reinecke <hare@suse.de>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2] scsi: megasas: initialise local configuration data buffer
Date: Tue, 7 Jun 2016 09:53:52 +0200 [thread overview]
Message-ID: <8a644c05-e43d-0a37-4f10-323abb892701@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1606071217140.5446@wniryva>
On 07/06/2016 08:51, P J P wrote:
> +-- On Wed, 25 May 2016, P J P wrote --+
> | Update as per
> | -> https://lists.gnu.org/archive/html/qemu-devel/2016-05/msg04402.html
> |
> | diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
> | index dcbd3e1..bf642d4 100644
> | --- a/hw/scsi/megasas.c
> | +++ b/hw/scsi/megasas.c
> | @@ -1293,7 +1293,7 @@ static int megasas_dcmd_ld_get_info(MegasasState *s, MegasasCmd *cmd)
> |
> | static int megasas_dcmd_cfg_read(MegasasState *s, MegasasCmd *cmd)
> | {
> | - uint8_t data[4096];
> | + uint8_t data[4096] = { 0 };
> | struct mfi_config_data *info;
> | int num_pd_disks = 0, array_offset, ld_offset;
> | BusChild *kid;
>
> Ping..!
>
> This one came with couple of others,
>
> -> https://patchwork.ozlabs.org/patch/626089/
> -> https://patchwork.ozlabs.org/patch/626152/
> -> https://patchwork.ozlabs.org/patch/626151/
>
> Are these queued? (just checking)
They are in already. In particular this is commit
d37af740730dbbb93960cd318e040372d04d6dcf.
Paolo
next prev parent reply other threads:[~2016-06-07 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 12:11 [Qemu-devel] [PATCH v2] scsi: megasas: initialise local configuration data buffer P J P
2016-06-07 6:51 ` P J P
2016-06-07 7:53 ` Paolo Bonzini [this message]
2016-06-07 8:48 ` 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=8a644c05-e43d-0a37-4f10-323abb892701@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=hare@suse.de \
--cc=liqiang6-s@360.cn \
--cc=ppandit@redhat.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 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).