From: zhong jiang <zhongjiang@huawei.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Himanshu Jha <himanshujha199640@gmail.com>,
Gilles Muller <Gilles.Muller@lip6.fr>, <nicolas.palix@imag.fr>,
<michal.lkml@markovi.net>, <yamada.masahiro@socionext.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Coccinelle: remove pci_alloc_consistent semantic to dectect in zalloc-simple.cocci
Date: Sat, 18 Aug 2018 22:10:26 +0800 [thread overview]
Message-ID: <5B7828D2.5010506@huawei.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1808181600470.2348@hadrien>
On 2018/8/18 22:01, Julia Lawall wrote:
>
> On Sat, 18 Aug 2018, zhong jiang wrote:
>
>> On 2018/8/18 20:52, Himanshu Jha wrote:
>>> On Sat, Aug 18, 2018 at 08:01:40PM +0800, zhong jiang wrote:
>>>> Because pci_alloc_consistent has been deprecated. We prefer to use
>>>> dam_alloc_coherent directly. Therefore, we should remove pci_alloc_consistent
>>> ^^^ typo "dma"
>>>
>>> Also, typo in the patch subject "dectect" -> "detect"
>> Thanks, will fix it in v2.
>>> Otherwise,
>>>
>>> Acked-by: Himanshu Jha <himanshujha199640@gmail.com>
>>>
>>> Thanks for cleaning up, we still have few more *_alloc/memset
>>> in the mainline, especially in the scsi subsystem, even after
>>> I cleaned up with two long patch series in the past.
>>>
>> I post same patches like *_alloc/memset in the scsi subsystem. Unfortunately,
>> Maintainer maybe do not care about the change. therefore, None of my patches
>> are received and rarely feedback.
> Maybe they will be picked up later.
Hope so. It's been more than a month since I post the patches. Maybe I should give a kindly ping. :-)
Thanks,
zhong jiang
> julia
>
> .
>
next prev parent reply other threads:[~2018-08-18 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 12:01 zhong jiang
2018-08-18 12:19 ` Julia Lawall
2018-08-18 12:52 ` Himanshu Jha
2018-08-18 13:56 ` zhong jiang
2018-08-18 14:01 ` Julia Lawall
2018-08-18 14:10 ` zhong jiang [this message]
2018-08-18 14:52 ` Himanshu Jha
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=5B7828D2.5010506@huawei.com \
--to=zhongjiang@huawei.com \
--cc=Gilles.Muller@lip6.fr \
--cc=himanshujha199640@gmail.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nicolas.palix@imag.fr \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®