From: Jason Gunthorpe <jgg@nvidia.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: benve@cisco.com, neescoba@cisco.com, pkaustub@cisco.com,
dledford@redhat.com, hch@infradead.org,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] RDMA/usnic: switch from 'pci_' to 'dma_' API
Date: Thu, 16 Jul 2020 18:44:35 +0000 [thread overview]
Message-ID: <20200716184435.GA2670424@nvidia.com> (raw)
In-Reply-To: <20200711073120.249146-1-christophe.jaillet@wanadoo.fr>
On Sat, Jul 11, 2020 at 09:31:20AM +0200, Christophe JAILLET wrote:
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script bellow.
> It has been compile tested.
>
> When memory is allocated, GFP_ATOMIC should be used to be consistent with
> the surrounding code.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> If needed, see post from Christoph Hellwig on the kernel-janitors ML:
> https://marc.info/?l=kernel-janitors&m\x158745678307186&w=4
> ---
> drivers/infiniband/hw/usnic/usnic_fwd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I checked the GFP and it looks OK to me, thanks.
Applied to for-next
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: <benve@cisco.com>, <neescoba@cisco.com>, <pkaustub@cisco.com>,
<dledford@redhat.com>, <hch@infradead.org>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] RDMA/usnic: switch from 'pci_' to 'dma_' API
Date: Thu, 16 Jul 2020 15:44:35 -0300 [thread overview]
Message-ID: <20200716184435.GA2670424@nvidia.com> (raw)
In-Reply-To: <20200711073120.249146-1-christophe.jaillet@wanadoo.fr>
On Sat, Jul 11, 2020 at 09:31:20AM +0200, Christophe JAILLET wrote:
> The wrappers in include/linux/pci-dma-compat.h should go away.
>
> The patch has been generated with the coccinelle script bellow.
> It has been compile tested.
>
> When memory is allocated, GFP_ATOMIC should be used to be consistent with
> the surrounding code.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> If needed, see post from Christoph Hellwig on the kernel-janitors ML:
> https://marc.info/?l=kernel-janitors&m=158745678307186&w=4
> ---
> drivers/infiniband/hw/usnic/usnic_fwd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I checked the GFP and it looks OK to me, thanks.
Applied to for-next
Jason
next prev parent reply other threads:[~2020-07-16 18:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 7:31 [PATCH] RDMA/usnic: switch from 'pci_' to 'dma_' API Christophe JAILLET
2020-07-11 7:31 ` Christophe JAILLET
2020-07-11 10:04 ` Markus Elfring
2020-07-11 10:04 ` Markus Elfring
2020-07-16 18:44 ` Jason Gunthorpe [this message]
2020-07-16 18:44 ` Jason Gunthorpe
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=20200716184435.GA2670424@nvidia.com \
--to=jgg@nvidia.com \
--cc=benve@cisco.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dledford@redhat.com \
--cc=hch@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neescoba@cisco.com \
--cc=pkaustub@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.