All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org
Subject: Re: [PATCH] sound: fix oss/msnd_pinnacle module param type
Date: Thu, 29 Mar 2012 18:00:20 +0200	[thread overview]
Message-ID: <s5hlimjtn1n.wl%tiwai@suse.de> (raw)
In-Reply-To: <4F73BA35.7010009@xenotime.net>

At Wed, 28 Mar 2012 18:26:13 -0700,
Randy Dunlap wrote:
> 
> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Fix module parameter data type to eliminate build warning.
> 
> sound/oss/msnd_pinnacle.c:1727:1: warning: return from incompatible pointer type
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>

Applied now.  Thanks.


Takashi

> ---
>  sound/oss/msnd_pinnacle.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20120328.orig/sound/oss/msnd_pinnacle.c
> +++ linux-next-20120328/sound/oss/msnd_pinnacle.c
> @@ -1631,7 +1631,7 @@ static int ide_irq __initdata = 0;
>  static int joystick_io __initdata = 0;
>  
>  /* If we have the digital daugherboard... */
> -static int digital __initdata = 0;
> +static bool digital __initdata = false;
>  #endif
>  
>  static int fifosize __initdata =	DEFFIFOSIZE;
> 

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sound: fix oss/msnd_pinnacle module param type
Date: Thu, 29 Mar 2012 18:00:20 +0200	[thread overview]
Message-ID: <s5hlimjtn1n.wl%tiwai@suse.de> (raw)
In-Reply-To: <4F73BA35.7010009@xenotime.net>

At Wed, 28 Mar 2012 18:26:13 -0700,
Randy Dunlap wrote:
> 
> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Fix module parameter data type to eliminate build warning.
> 
> sound/oss/msnd_pinnacle.c:1727:1: warning: return from incompatible pointer type
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>

Applied now.  Thanks.


Takashi

> ---
>  sound/oss/msnd_pinnacle.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20120328.orig/sound/oss/msnd_pinnacle.c
> +++ linux-next-20120328/sound/oss/msnd_pinnacle.c
> @@ -1631,7 +1631,7 @@ static int ide_irq __initdata = 0;
>  static int joystick_io __initdata = 0;
>  
>  /* If we have the digital daugherboard... */
> -static int digital __initdata = 0;
> +static bool digital __initdata = false;
>  #endif
>  
>  static int fifosize __initdata =	DEFFIFOSIZE;
> 

  reply	other threads:[~2012-03-29 16:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28  6:14 linux-next: Tree for Mar 28 Stephen Rothwell
2012-03-29  1:26 ` [PATCH] sound: fix oss/msnd_pinnacle module param type Randy Dunlap
2012-03-29  1:26   ` Randy Dunlap
2012-03-29 16:00   ` Takashi Iwai [this message]
2012-03-29 16:00     ` Takashi Iwai
2012-03-29  1:26 ` [PATCH] sound: fix isa/opti9xx " Randy Dunlap
2012-03-29  1:26   ` Randy Dunlap
2012-03-29 16:00   ` Takashi Iwai

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=s5hlimjtn1n.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sfr@canb.auug.org.au \
    /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.