linux-kernel - Re: linux-next: build failure after merge of the mfd tree

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 31 May 2017 13:36:30 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Darren Hart <dvhart@...radead.org>
Cc:     Lee Jones <lee.jones@...aro.org>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Kuppuswamy Sathyanarayanan 
        <sathyanarayanan.kuppuswamy@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the mfd tree

Hi Darren,

On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
> drivers/usb/typec/typec_wcove.c:306:32: error: 'struct intel_soc_pmic' has no member named 'irq_chip_data_level2'
>   ret = regmap_irq_get_virq(pmic->irq_chip_data_level2,
>                                 ^
> 
> Caused by commit
> 
>   aa32452e6ef9 ("mfd: intel_soc_pmic_bxtwc: Use chained irqs for second level irq chips")
> 
> interacting with commit
> 
>   d2061f9cc32d ("usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY")
> 
> from Linus' tree (v4.12-rc1).  grep is your friend. :-)
> 
> I have used the mfd tree from next-20170530 for today.

This also affected the drivers-x86 tree, so I have use the version of
that from next-20170530 as well.

-- 
Cheers,
Stephen Rothwell