public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: hverkuil@xs4all.nl, linux-media@vger.kernel.org,
	davinci-linux-open-source@linux.davincidsp.com
Subject: Re: [PATCH] V4L/DVB: dm646x: fix DMA_nnBIT_MASK
Date: Mon, 10 Aug 2009 14:23:08 -0700	[thread overview]
Message-ID: <87r5vjfjnn.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1248389413-19366-1-git-send-email-khilman@deeprootsystems.com> (Kevin Hilman's message of "Thu\, 23 Jul 2009 15\:50\:13 -0700")

Kevin Hilman <khilman@deeprootsystems.com> writes:

> Fix deprecated use of DMA_nnBIT_MASK which now gives a compiler
> warning.
>
> Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
> ---
> This compiler warning patch is on top of the master branch of Mauro's 
> linux-next tree.

Ping. 

This is needed on top of the DaVinci changes queued in the master branch
of Mauro's linux-next.git.

Kevin

>  arch/arm/mach-davinci/dm646x.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-davinci/dm646x.c b/arch/arm/mach-davinci/dm646x.c
> index 73a7e8b..8f38371 100644
> --- a/arch/arm/mach-davinci/dm646x.c
> +++ b/arch/arm/mach-davinci/dm646x.c
> @@ -720,7 +720,7 @@ static struct platform_device vpif_display_dev = {
>  	.id		= -1,
>  	.dev		= {
>  			.dma_mask 		= &vpif_dma_mask,
> -			.coherent_dma_mask	= DMA_32BIT_MASK,
> +			.coherent_dma_mask	= DMA_BIT_MASK(32),
>  	},
>  	.resource	= vpif_resource,
>  	.num_resources	= ARRAY_SIZE(vpif_resource),
> -- 
> 1.6.3.3

      reply	other threads:[~2009-08-10 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 22:50 [PATCH] V4L/DVB: dm646x: fix DMA_nnBIT_MASK Kevin Hilman
2009-08-10 21:23 ` Kevin Hilman [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=87r5vjfjnn.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    /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