Re: linux-next: build failure after merge of the usb.current tree

[Greg KH]

On Wed, Aug 27, 2014 at 11:03:22AM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the usb.current tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
> 
> drivers/usb/core/hub.c: In function 'hub_probe':
> drivers/usb/core/hub.c:1735:21: error: 'struct dev_pm_info' has no member 
> named 'autosuspend_delay'
>   if (hdev->dev.power.autosuspend_delay >= 0)
>  ^
> 
> Caused by commit bdd405d2a528 ("usb: hub: Prevent hub autosuspend if
> usbcore.autosuspend is -1").  CONFIG_PM_RUNTIME is not set in this
> build.
> 
> I have reverted that commit for today.

Thanks, I'll work on fixing this later on today...

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: build failure after merge of the usb.current tree

[Greg KH]

On Wed, Aug 27, 2014 at 11:03:22AM +1000, Stephen Rothwell wrote:
 Hi Greg,
 
 After merging the usb.current tree, today's linux-next build (powerpc
 ppc64_defconfig) failed like this:
 
 drivers/usb/core/hub.c: In function 'hub_probe':
 drivers/usb/core/hub.c:1735:21: error: 'struct dev_pm_info' has no member 
 named 'autosuspend_delay'
   if (hdev-dev.power.autosuspend_delay = 0)
  ^
 
 Caused by commit bdd405d2a528 (usb: hub: Prevent hub autosuspend if
 usbcore.autosuspend is -1).  CONFIG_PM_RUNTIME is not set in this
 build.
 
 I have reverted that commit for today.

Thanks, I'll work on fixing this later on today...

greg k-h
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/