public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Mauro Carvalho Chehab <mchehab@infradead•org>
Cc: linux-next@vger•kernel.org,
	Devin Heitmueller <devin.heitmueller@gmail•com>
Subject: linux-next: v4l-dvb tree build failure
Date: Tue, 25 Nov 2008 15:41:55 +1100	[thread overview]
Message-ID: <20081125154155.4e547cd0.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

Hi Mauro,

Today's linux-next build (x86_64 allmodconfig) failed like this:

drivers/media/video/em28xx/em28xx-core.c: In function 'em28xx_set_audio_source':
drivers/media/video/em28xx/em28xx-core.c:372: error: 'video' undeclared (first use in this function)
drivers/media/video/em28xx/em28xx-core.c:372: error: 'disable' undeclared (first use in this function)
drivers/media/video/em28xx/em28xx-core.c:373: error: 'line' undeclared (first use in this function)
drivers/media/video/em28xx/em28xx-core.c:373: error: 'enable' undeclared (first use in this function)

Caused by a bad merge of commits
3f9b46c154da5ec4facca88f82d1820eb329fd3e ("V4L/DVB (9632): make em28xx
aux audio input work") and 2173b4ae6f8262d15fc933a13191cd6d5e789e8d
("V4L/DVB (9651): em28xx: Improve audio handling").

I have dropped the v4l-dvb tree for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-11-25  4:42 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  4:41 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-27  6:59 linux-next: v4l-dvb tree build failure Stephen Rothwell
2010-01-27 23:24 ` Andy Walls
2010-01-28  1:54   ` Mauro Carvalho Chehab
2010-01-28  5:24     ` Stephen Rothwell
2009-04-07  0:58 Stephen Rothwell
2009-04-07  1:20 ` Mauro Carvalho Chehab
2009-04-07  4:47   ` Stephen Rothwell
2009-03-27  0:40 Stephen Rothwell
2009-03-27 11:28 ` Mauro Carvalho Chehab
2009-03-27 14:03   ` Stephen Rothwell
2009-03-05  0:35 Stephen Rothwell
2009-03-05 21:51 ` Mauro Carvalho Chehab
2009-03-06  0:05   ` Stephen Rothwell
2009-03-06  1:15     ` Mauro Carvalho Chehab
2009-03-02  0:05 Stephen Rothwell
2009-03-02  0:08 ` Michael Krufky
2009-03-02  0:30   ` Stephen Rothwell
2009-03-02  2:52     ` Mauro Carvalho Chehab
2008-12-08  2:07 Stephen Rothwell
2008-12-01 23:37 Stephen Rothwell
2008-12-02 10:03 ` Mauro Carvalho Chehab
2008-12-02 22:23   ` Stephen Rothwell
2008-12-03 22:48     ` Mauro Carvalho Chehab
2008-12-03  0:08   ` Stephen Rothwell
2008-12-03 22:49     ` Mauro Carvalho Chehab
2008-11-07  3:30 Stephen Rothwell
2008-11-07 17:43 ` Harvey Harrison
2008-11-07 18:41   ` Greg KH
2008-11-07 23:02     ` Stephen Rothwell
2008-11-12  0:54     ` Mauro Carvalho Chehab
2008-11-12 22:45       ` Greg KH
2008-11-07 22:59   ` Stephen Rothwell
2008-11-07 23:06     ` Greg KH
2008-11-08  3:05     ` Sam Ravnborg
2008-11-08  4:38       ` Greg KH
2008-11-08  5:08         ` Greg KH
2008-10-29  2:20 Stephen Rothwell
2008-10-29 12:26 ` Andreas Oberritter
2008-11-03  1:52 ` Stephen Rothwell
2008-11-05  1:57   ` 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=20081125154155.4e547cd0.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=devin.heitmueller@gmail$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mchehab@infradead$(echo .)org \
    /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