From: John Garry <john.garry@huawei.com>
To: zhong jiang <zhongjiang@huawei.com>, <jejb@linux.vnet.ibm.com>,
<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] driver/scsi/pmcraid: Use pci_zalloc_consistent instead of pci_alloc_consistent+memset
Date: Wed, 1 Aug 2018 16:27:49 +0800 [thread overview]
Message-ID: <eb0a5e82-a67d-4176-12e6-607fb17a4e5d@huawei.com> (raw)
In-Reply-To: <1533107805-7545-1-git-send-email-zhongjiang@huawei.com>
在 2018/8/1 15:16, zhong jiang 写道:
> Pci_zalloc_consistent is better than pci_alloc_consistent+memset,
> and it make the code concise
Aren't these APIs deprecated:
https://lkml.org/lkml/2018/6/5/381
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> ---
> drivers/scsi/pmcraid.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
> index 4e86994..8a6facc 100644
> --- a/drivers/scsi/pmcraid.c
> +++ b/drivers/scsi/pmcraid.c
> @@ -4736,11 +4736,9 @@ static int pmcraid_allocate_host_rrqs(struct pmcraid_instance *pinstance)
> buffer_size = HRRQ_ENTRY_SIZE * PMCRAID_MAX_CMD;
>
> for (i = 0; i < pinstance->num_hrrq; i++) {
> - pinstance->hrrq_start[i] =
> - pci_alloc_consistent(
> - pinstance->pdev,
> - buffer_size,
> - &(pinstance->hrrq_start_bus_addr[i]));
> + pinstance->hrrq_start[i] = pci_zalloc_consistent(pinstance->pdev,
> + buffer_size,
> + &(pinstance->hrrq_start_bus_addr[i]));
>
> if (!pinstance->hrrq_start[i]) {
> pmcraid_err("pci_alloc failed for hrrq vector : %d\n",
> @@ -4749,7 +4747,6 @@ static int pmcraid_allocate_host_rrqs(struct pmcraid_instance *pinstance)
> return -ENOMEM;
> }
>
> - memset(pinstance->hrrq_start[i], 0, buffer_size);
> pinstance->hrrq_curr[i] = pinstance->hrrq_start[i];
> pinstance->hrrq_end[i] =
> pinstance->hrrq_start[i] + PMCRAID_MAX_CMD - 1;
>
next prev parent reply other threads:[~2018-08-01 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 7:16 zhong jiang
2018-08-01 8:27 ` John Garry [this message]
2018-08-01 9:14 ` zhong jiang
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=eb0a5e82-a67d-4176-12e6-607fb17a4e5d@huawei.com \
--to=john.garry@huawei.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=zhongjiang@huawei.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
Powered by JetHome