From: Sebastian Herbszt <herbszt@gmx.de>
To: James Smart <james.smart@avagotech.com>
Cc: linux-scsi@vger.kernel.org, Sebastian Herbszt <herbszt@gmx.de>
Subject: Re: [PATCH 16/17] lpfc: Use kzalloc instead of kmalloc
Date: Thu, 17 Dec 2015 23:58:58 +0100 [thread overview]
Message-ID: <20151217235858.00004089@localhost> (raw)
In-Reply-To: <5671efc7.97bycJ6w84wBFCRH%james.smart@avagotech.com>
James Smart wrote:
> From: Punit Vara <punitvara@gmail.com>
>
> This patch is to the lpfc_els.c which resolves following warning
> reported by coccicheck:
>
> WARNING: kzalloc should be used for rdp_context, instead of
> kmalloc/memset
>
> Signed-off-by: Punit Vara <punitvara@gmail.com>
> Signed-off-by: James Smart <james.smart@avagotech.com>
You missed the two already available positive reviews [1][2].
Anyway,
Reviewed-by: Sebastian Herbszt <herbszt@gmx.de>
[1] http://marc.info/?l=linux-scsi&m=144574360607327&w=2
[2] http://marc.info/?l=linux-scsi&m=144823385015994&w=2
prev parent reply other threads:[~2015-12-17 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 23:12 [PATCH 16/17] lpfc: Use kzalloc instead of kmalloc James Smart
2015-12-17 0:04 ` Matthew R. Ochs
2015-12-17 8:39 ` Hannes Reinecke
2015-12-17 22:58 ` Sebastian Herbszt [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=20151217235858.00004089@localhost \
--to=herbszt@gmx.de \
--cc=james.smart@avagotech.com \
--cc=linux-scsi@vger.kernel.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