From: P J P <ppandit@redhat.com>
To: Qemu Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, 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 12:21:41 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1606071217140.5446@wniryva> (raw)
In-Reply-To: <1464178304-12831-1-git-send-email-ppandit@redhat.com>
+-- 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)
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-06-07 6:51 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 [this message]
2016-06-07 7:53 ` Paolo Bonzini
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=alpine.LFD.2.20.1606071217140.5446@wniryva \
--to=ppandit@redhat.com \
--cc=agraf@suse.de \
--cc=hare@suse.de \
--cc=liqiang6-s@360.cn \
--cc=pbonzini@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).