public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Takashi Iwai <tiwai@suse.de>,
	Alsa-devel <alsa-devel@lists.sourceforge.net>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-sh <linux-sh@vger.kernel.org>
Subject: Re: [PATCH] snd: aica - fix annoying compiler warning
Date: Thu, 02 Apr 2009 00:41:50 +0100	[thread overview]
Message-ID: <1238629310.7455.0.camel@localhost.localdomain> (raw)
In-Reply-To: <20090330231043.GF19535@linux-sh.org>

On Tue, 2009-03-31 at 08:10 +0900, Paul Mundt wrote:
> On Mon, Mar 16, 2009 at 08:59:20AM +0100, Takashi Iwai wrote:
> > At Mon, 16 Mar 2009 07:54:09 +0000,
> > Adrian McMenamin wrote:
> > > 
> > > On Mon, 2009-03-16 at 07:31 +0100, Takashi Iwai wrote:
> > > > At Sun, 15 Mar 2009 22:05:40 +0000,
> > > > Adrian McMenamin wrote:
> > > > > 
> > > > > Cast pointer to data member of struct firmware as a void to end an
> > > > > annoying compiler warning.
> > > > > 
> > > > > fix annoying compiler warning
> > > > > 
> > > > > Signed-off-by: Adrian McMenamin <adrian@mcmen.demon.co.uk>
> > > > > ---
> > > > > 
> > > > > diff --git a/sound/sh/aica.c b/sound/sh/aica.c
> > > > > index 7c920f3..822b119 100644
> > > > > --- a/sound/sh/aica.c
> > > > > +++ b/sound/sh/aica.c
> > > > > @@ -567,7 +567,7 @@ static int load_aica_firmware(void)
> > > > >  		return err;
> > > > >  	/* write firware into memory */
> > > > >  	spu_disable();
> > > > > -	spu_memload(0, fw_entry->data, fw_entry->size);
> > > > > +	spu_memload(0, (void *)fw_entry->data, fw_entry->size);
> > > > 
> > > > IMO, it's better to fix spu_memload() to take const pointer instead of 
> > > > cast.
> > > > 
> > > 
> > > If that's what you want I can do that but it adds to kernel bloat by
> > > having two functions essentially do the same thing.
> > 
> > I meant a fix like below...
> > 
> Is anything happening with this, or should I just ignore it? 
> 

I though Takashi's fix was fine/obvious but it doesn't appear to have
been pushed upstream (yet?)


  reply	other threads:[~2009-04-01 23:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 22:05 [PATCH] snd: aica - fix annoying compiler warning Adrian McMenamin
2009-03-16  6:31 ` Takashi Iwai
2009-03-16  7:54   ` Adrian McMenamin
2009-03-16  7:59     ` Takashi Iwai
2009-03-30 23:10       ` Paul Mundt
2009-04-01 23:41         ` Adrian McMenamin [this message]
2009-04-06  1:28           ` 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=1238629310.7455.0.camel@localhost.localdomain \
    --to=adrian@newgolddream.dyndns.info \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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