public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Luiz Fernando Capitulino <lcapitulino@mandriva.com.br>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, kraxel@bytesex.org,
	Linux and Kernel Video <video4linux-list@redhat.com>
Subject: Re: [PATCH] - Fixes sparse warning in bttv-driver.
Date: Wed, 16 Nov 2005 17:47:30 -0200	[thread overview]
Message-ID: <1132170450.9041.110.camel@localhost> (raw)
In-Reply-To: <20051114095440.5fb13e00.lcapitulino@mandriva.com.br>

Luiz Fernando,

	Please send V4L fixes to me instead of Kraxel or to V4L mailing list
(video4linux-list@redhat.com). I'm the current V4L maintainer.

Cheers,
Mauro.

Em Seg, 2005-11-14 às 09:54 -0200, Luiz Fernando Capitulino escreveu:
> Hi,
> 
> The patch below fixes the following sparse warning:
> 
> drivers/media/video/bttv-driver.c
> 
> Signed-off-by: Luiz Capitulino <lcapitulino@mandriva.com.br>
Acked-by: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
> 
>  drivers/media/video/bttv-driver.c |    2 +-
>  drivers/media/video/bttv-i2c.c    |    0 
	?
>  2 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/media/video/bttv-driver.c b/drivers/media/video/bttv-driver.c
> --- a/drivers/media/video/bttv-driver.c
> +++ b/drivers/media/video/bttv-driver.c
> @@ -1853,7 +1853,7 @@ static int bttv_common_ioctls(struct btt
>  	}
>  	case VIDIOC_LOG_STATUS:
>  	{
> -		bttv_call_i2c_clients(btv, VIDIOC_LOG_STATUS, 0);
> +		bttv_call_i2c_clients(btv, VIDIOC_LOG_STATUS, NULL);
>  		return 0;
>  	}
>  
> diff --git a/drivers/media/video/bttv-i2c.c b/drivers/media/video/bttv-i2c.c
	?


      reply	other threads:[~2005-11-16 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 11:54 [PATCH] - Fixes sparse warning in bttv-driver Luiz Fernando Capitulino
2005-11-16 19:47 ` Mauro Carvalho Chehab [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=1132170450.9041.110.camel@localhost \
    --to=mchehab@brturbo.com.br \
    --cc=akpm@osdl.org \
    --cc=kraxel@bytesex.org \
    --cc=lcapitulino@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=video4linux-list@redhat.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