public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse•de>
To: Subrata Modak <subrata@linux•vnet.ibm.com>
Cc: Ingo Molnar <mingo@elte•hu>,
	linux-kernel <linux-kernel@vger•kernel.org>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	sachinp <sachinp@linux•vnet.ibm.com>,
	linux-next <linux-next@vger•kernel.org>
Subject: Re: [BUILD FAILURE 03] Next April 9 : x86_64 randconfig [drivers/staging/go7007/go7007-driver.c]
Date: Thu, 9 Apr 2009 08:26:40 -0700	[thread overview]
Message-ID: <20090409152640.GB4475@suse.de> (raw)
In-Reply-To: <1239286279.5188.74.camel@subratamodak.linux.ibm.com>

On Thu, Apr 09, 2009 at 07:41:19PM +0530, Subrata Modak wrote:
> Observed the following build error:
> 
> CC drivers/staging/go7007/go7007-driver.o
> drivers/staging/go7007/go7007-driver.c: In function
> ‘go7007_register_encoder’:
> drivers/staging/go7007/go7007-driver.c:284: error: ‘TUNER_SET_TYPE’
> undeclared (first use in this function)
> drivers/staging/go7007/go7007-driver.c:284: error: (Each undeclared
> identifier is reported only once
> drivers/staging/go7007/go7007-driver.c:284: error: for each function it
> appears in.)
> make[3]: *** [drivers/staging/go7007/go7007-driver.o] Error 1
> make[2]: *** [drivers/staging/go7007] Error 2
> make[1]: *** [drivers/staging] Error 2
> make: *** [drivers] Error 2

Thanks, I see this here now with the 2.6.30-rc1 release.  It was due to
some v4l api changes, I'll fix it up.

thanks,

greg k-h

      reply	other threads:[~2009-04-09 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 10:24 [BUILD FAILURE 02] Next April 9 : x86_64 randconfig [arch/x86/kernel/apic/io_apic.c] Subrata Modak
2009-04-09 14:11 ` [BUILD FAILURE 03] Next April 9 : x86_64 randconfig [drivers/staging/go7007/go7007-driver.c] Subrata Modak
2009-04-09 15:26   ` Greg KH [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=20090409152640.GB4475@suse.de \
    --to=gregkh@suse$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=sachinp@linux$(echo .)vnet.ibm.com \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=subrata@linux$(echo .)vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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