linux-kernel - Re: linux-next: usb/pxa trees build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 18 Aug 2009 04:42:42 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Eric Miao <eric.y.miao@...il.com>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Aric D. Blumer" <aric@...systems.com>,
	Mike Rapoport <mike@...pulab.co.il>,
	Russell King <rmk@....linux.org.uk>
Subject: Re: linux-next: usb/pxa trees build failure

On Tue, Aug 18, 2009 at 01:58:52PM +1000, Stephen Rothwell wrote:
> Hi Eric, Greg,
> 
> The next-20090817 (and a few before) build (arm trizeps4_defconfig)
> failed like this:
> 
> drivers/usb/host/ohci-pxa27x.c:507: error: 'pdev' undeclared (first use in this function)
> 
> Caused by the interaction of commit
> 6458baec17e19d38b9d4eb1f96c213f91609c0e3 ("USB: ohci-pxa27x: Reconfigure
> power settings on resume") from the usb tree with commit
> b8fb7d4317bcea1b48c9560d23dff81121870ece ("[ARM] pxa: update
> ohci-pxa27x.c to use 'struct dev_pm_ops'"). from the pxa tree.
> 
> Greg/Aric, maybe that usb tree patch needs to go through the pxa tree?
> (and maybe "USB: ohci-pxa27x: Allow NOCP and OCPM to be cleared" as well?)
> 
> [this also broke the following configs: magician_defconfig,
> em_x270_defconfig and cm_x2xx_defconfig.]

Ick, not good.  Aric, should I drop this patch from my tree?

thanks,

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