All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Ren, Yongjie" <yongjie.ren@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM make error--drivers/usb/serial/usb_wwan.c
Date: Wed, 23 Mar 2011 11:02:21 +0200	[thread overview]
Message-ID: <4D89B71D.5030900@redhat.com> (raw)
In-Reply-To: <CE59C043D0EC3349B2BF41C0EC72229B4B28E11F@shsmsx501.ccr.corp.intel.com>

On 03/23/2011 04:41 AM, Ren, Yongjie wrote:
> Hi folks,
> Kvm.git: commit 2ee44a580db58f98d85b57bfc468bbc5729ec9b3  Author: Avi Kivity    Date:   Mon Mar 21 12:53:58 2011 +0200
> My build system: RHEL5u5,  Linux kvm-build 2.6.38-rc4+ #1 SMP Sat Feb 19 15:35:09 CST 2011 x86_64 x86_64 x86_64 GNU/Linux
>
> When I make kvm, I get the following error.
> drivers/usb/serial/usb_wwan.c: In function 'play_delayed':
> drivers/usb/serial/usb_wwan.c:702: error: 'struct dev_pm_info' has no member named 'usage_count'
>
> And I look at the 702Row of usb_wwan.c    It shows:
> atomic_dec(&port->serial->interface->dev.power.usage_count);
> I see usage_count is declared in kvm.git/include/linux/pm.h , but it is declared between "#ifdef" and "#endif".   #ifdef CONFIG_PM_RUNTIME .
> Kernel of build system doesn't define CONFIG_PM_RUNTIME, so I got the kvm make error.
>
> Anybody knows the solution ?  Thanks.
>

I suggest simply disabling this driver.  A simple way is 'make 
localmodconfig' which disables all drivers not currently in use (and 
makes for a much faster build as well).

The problem will likely go away on the next merge from linux-2.6.git.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2011-03-23  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  2:41 KVM make error--drivers/usb/serial/usb_wwan.c Ren, Yongjie
2011-03-23  9:02 ` Avi Kivity [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=4D89B71D.5030900@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=yongjie.ren@intel.com \
    /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.