From: James Bottomley <jejb@linux.vnet.ibm.com>
To: Sabyasachi Gupta <sabyasachi.linux@gmail.com>, akpm@linux-foundation.org
Cc: aacraid@microsemi.com, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
jrdr.linux@gmail.com
Subject: Re: [PATCH] scsi/dpt_i2o.c: Use dma_zalloc_coherent
Date: Mon, 11 Mar 2019 09:13:49 -0700 [thread overview]
Message-ID: <1552320829.2889.11.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <5c8683f7.1c69fb81.e37f9.75a0@mx.google.com>
On Mon, 2019-03-11 at 21:21 +0530, Sabyasachi Gupta wrote:
> Replaced dma_alloc_coherent + memset with dma_zalloc_coherent
I really don't think so. This API is going away:
https://lkml.org/lkml/2019/1/8/394
James
next prev parent reply other threads:[~2019-03-11 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 15:51 [PATCH] scsi/dpt_i2o.c: Use dma_zalloc_coherent Sabyasachi Gupta
2019-03-11 16:13 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-17 12:47 Sabyasachi Gupta
2018-12-01 13:15 ` Sabyasachi Gupta
2018-12-19 13:11 ` Sabyasachi Gupta
2019-01-04 12:49 ` Sabyasachi Gupta
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=1552320829.2889.11.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=aacraid@microsemi.com \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sabyasachi.linux@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