From: "Kumar, M Chetan" <m.chetan.kumar@intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
linuxwwan@intel.com, loic.poulain@linaro.org,
ryazanov.s.a@gmail.com, johannes@sipsolutions.net,
davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: wwan: iosm: switch from 'pci_' to 'dma_' API
Date: Tue, 13 Jul 2021 10:28:48 +0530 [thread overview]
Message-ID: <754912a3-d1fe-516f-d64b-e8a70a93d570@intel.com> (raw)
In-Reply-To: <dd34ecd3c8afe5a9a29e026035a4a11c63e033ae.1626014972.git.christophe.jaillet@wanadoo.fr>
On 7/11/2021 8:21 PM, Christophe JAILLET wrote:
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script below and has been
> hand modified to replace GFP_ with a correct flag.
> It has been compile tested.
>
> When memory is allocated in 'ipc_protocol_init()' GFP_KERNEL can be used
> because this flag is already used a few lines above and no lock is
> acquired in the between.
>
> When memory is allocated in 'ipc_protocol_msg_prepipe_open()' GFP_ATOMIC
> should be used because this flag is already used a few lines above.
Thanks,
Reviewed-by: M Chetan Kumar <m.chetan.kumar@intel.com>
Regards,
Chetan
next prev parent reply other threads:[~2021-07-13 4:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 14:51 [PATCH] net: wwan: iosm: switch from 'pci_' to 'dma_' API Christophe JAILLET
2021-07-13 4:58 ` Kumar, M Chetan [this message]
2021-08-21 20:54 Christophe JAILLET
2021-08-23 11:00 ` patchwork-bot+netdevbpf
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=754912a3-d1fe-516f-d64b-e8a70a93d570@intel.com \
--to=m.chetan.kumar@intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxwwan@intel.com \
--cc=loic.poulain@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=ryazanov.s.a@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;
as well as URLs for NNTP newsgroup(s).