public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, mchehab@kernel.org
Subject: Re: [PATCH 2/2] omap3isp: Don't use GFP_DMA
Date: Mon, 07 May 2018 16:21:50 +0300	[thread overview]
Message-ID: <2190885.d6Gm8zIgfg@avalon> (raw)
In-Reply-To: <20180507124723.2153-3-sakari.ailus@linux.intel.com>

Hi Sakari,

Thank you for the patch.

On Monday, 7 May 2018 15:47:23 EEST Sakari Ailus wrote:
> The isp stat driver allocates memory for DMA and uses GFP_DMA flag for
> dev_alloc_coherent. The flag is no longer needed as the DMA mask is used
> for the purpose. Remove it.
> 
> Reported-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> ---
>  drivers/media/platform/omap3isp/ispstat.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/platform/omap3isp/ispstat.c
> b/drivers/media/platform/omap3isp/ispstat.c index
> 34a91125da36..c68562189961 100644
> --- a/drivers/media/platform/omap3isp/ispstat.c
> +++ b/drivers/media/platform/omap3isp/ispstat.c
> @@ -371,7 +371,7 @@ static int isp_stat_bufs_alloc_one(struct device *dev,
>  	int ret;
> 
>  	buf->virt_addr = dma_alloc_coherent(dev, size, &buf->dma_addr,
> -					    GFP_KERNEL | GFP_DMA);
> +					    GFP_KERNEL);
>  	if (!buf->virt_addr)
>  		return -ENOMEM;

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2018-05-07 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 12:47 [PATCH 0/2] omap3isp cleanups Sakari Ailus
2018-05-07 12:47 ` [PATCH 1/2] omap3isp: Remove useless NULL check in omap3isp_stat_config Sakari Ailus
2018-05-07 13:21   ` Laurent Pinchart
2018-05-07 12:47 ` [PATCH 2/2] omap3isp: Don't use GFP_DMA Sakari Ailus
2018-05-07 13:21   ` Laurent Pinchart [this message]

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=2190885.d6Gm8zIgfg@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.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