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-prev] [day] [month] [year] [list]
Date:	Thu, 28 May 2015 11:38:05 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Arend van Spriel <arend@...adcom.com>
Cc:	Kalle Valo <kvalo@...eaurora.org>, <linux-next@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>,
	"Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the
 wireless-drivers-next tree

Hi Arend,

On Wed, 27 May 2015 11:08:35 +0200 Arend van Spriel <arend@...adcom.com> wrote:
>
> On 05/27/15 04:03, Stephen Rothwell wrote:
> >
> > After merging the wireless-drivers-next tree, today's linux-next build
> > (arm multi_v7_defconfig) failed like this:
> >
> > drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c: In function 'brcmf_ops_sdio_probe':
> > drivers/net/wireless/brcm80211/brcmfmac/bcmsdh.c:1139:7: error: dereferencing pointer to incomplete type
> >     adev->flags.power_manageable = 0;
> >         ^
> >
> > Caused by commit f0992ace680c ("brcmfmac: prohibit ACPI power
> > management for brcmfmac driver").
> >
> > I have used the wireless-drivers-next from next-20150526 for today.
> 
> Crap. struct acpi_device details are only known when CONFIG_ACPI is set. 
> The attached patch should fix the issue.

I put that into linux-next today.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ