public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jonathan Corbet <corbet@lwn•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Mark Gross <mgross@linux•intel.com>
Subject: linux-next: build failure after merge of the viafb tree
Date: Tue, 25 May 2010 12:57:18 +1000	[thread overview]
Message-ID: <20100525125718.703fdc08.sfr@canb.auug.org.au> (raw)

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

Hi Jonathan,

After merging the viafb tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/media/video/via-camera.c: In function 'viacam_streamon':
drivers/media/video/via-camera.c:1032: error: implicit declaration of function 'pm_qos_add_requirement'
drivers/media/video/via-camera.c: In function 'viacam_streamoff':
drivers/media/video/via-camera.c:1052: error: implicit declaration of function 'pm_qos_remove_requirement'

Caused by commit d9acc26333e04633af61e634a5bd91c066162fca ("Add the viafb
video capture driver") interacting with commit
ed77134bfccf5e75b6cbadab268e559dbe6a4ebb ("PM QOS update") from Linus'
tree.  The pm_qos_..._requirement functions were renamed.

I have used the viafb tree from next-20100524 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

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

             reply	other threads:[~2010-05-25  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  2:57 Stephen Rothwell [this message]
2010-05-25 12:56 ` linux-next: build failure after merge of the viafb tree Jonathan Corbet
2010-05-25 13:30   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2010-09-20  3:10 Stephen Rothwell
2010-09-21  1:35 ` Florian Tobias Schandinat

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=20100525125718.703fdc08.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=corbet@lwn$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mgross@linux$(echo .)intel.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