All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the sound tree
Date: Fri, 23 Sep 2011 07:21:13 +0200	[thread overview]
Message-ID: <s5hr537g7g6.wl%tiwai@suse.de> (raw)
In-Reply-To: <20110923124934.dfde6643c66d33abdeeeedc9@canb.auug.org.au>

At Fri, 23 Sep 2011 12:49:34 +1000,
Stephen Rothwell wrote:
> 
> Hi Takashi,
> 
> After merging the sound tree, today's linux-next build ()
> failed like this:
> 
> sound/pci/fm801.c: In function 'snd_fm801_tea575x_get_pins':
> sound/pci/fm801.c:759:2: error: expected ',' or ';' before 'return'
> sound/pci/fm801.c:757:32: warning: unused variable 'gpio'
> sound/pci/fm801.c:756:17: warning: unused variable 'reg'
> sound/pci/fm801.c:761:1: warning: no return statement in function returning non-void
> sound/pci/fm801.c: In function 'snd_fm801_create':
> sound/pci/fm801.c:1251:5: error: implicit declaration of function 'get_tea57x_gpio'
> sound/pci/fm801.c:1251:5: error: invalid type argument of '->' (have 'int')
> 
> Caused by commit c51a94adef4c ("ALSA: fm801 - Clean up redundant reference to snd_fm801_tea575x_gpios[]").
> 
> I have used the sound tree from next-20110922 for today.

My bad, fixed now.


thanks,

Takashi

  reply	other threads:[~2011-09-23  5:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23  2:49 linux-next: build failure after merge of the sound tree Stephen Rothwell
2011-09-23  5:21 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-18  3:12 Stephen Rothwell
2023-08-18 11:47 ` Takashi Iwai
2023-05-24  3:54 Stephen Rothwell
2023-05-24  7:14 ` Takashi Iwai
2022-07-15 12:44 Stephen Rothwell
2022-07-15 14:41 ` Takashi Iwai
2022-07-15 19:09   ` Andy Shevchenko
2021-10-18  0:38 Stephen Rothwell
2021-10-18  6:35 ` Takashi Iwai
2020-07-17  3:01 Stephen Rothwell
2020-07-17  5:33 ` Christoph Hellwig
2020-07-17  6:34   ` Takashi Iwai
2020-07-17  6:50     ` Christoph Hellwig
2020-07-17  6:54       ` Takashi Iwai
2019-08-09  2:54 Stephen Rothwell
2019-08-09  5:55 ` Takashi Iwai
2017-05-17  1:29 Stephen Rothwell
2017-05-17  5:30 ` Takashi Iwai
2011-05-19  1:15 Stephen Rothwell
2010-09-23  2:44 Stephen Rothwell
2010-09-23  6:04 ` Takashi Iwai
2010-09-23  8:39   ` Mark Brown
2010-06-24  3:03 Stephen Rothwell
2010-06-24  6:11 ` Takashi Iwai
2010-06-28 16:33   ` Daniel Mack
2010-06-01  2:30 Stephen Rothwell
2010-06-01  5:47 ` Takashi Iwai
2010-04-07  3:39 Stephen Rothwell
2010-04-07  6:06 ` Takashi Iwai
2010-04-07  7:16   ` Stephen Rothwell

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=s5hr537g7g6.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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.