linux-kernel - Re: linux-next: build failure after merge of the phy-next 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] [day] [month] [year] [list]

Message-ID: <d9371bdc-4eb1-5bf0-6060-972e96daedf4@ti.com>
Date:   Thu, 30 Mar 2017 11:09:11 +0530
From:   Kishon Vijay Abraham I <kishon@...com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
CC:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Meng Dongyang <daniel.meng@...k-chips.com>
Subject: Re: linux-next: build failure after merge of the phy-next tree

Hi,

On Thursday 30 March 2017 09:17 AM, Stephen Rothwell wrote:
> Hi Kishon,
> 
> After merging the phy-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/phy/phy-rockchip-inno-usb2.c:1148:3: error: unknown field 'phy_tuning' specified in initializer
>    .phy_tuning = rk3328_usb2phy_tuning,
>    ^
> drivers/phy/phy-rockchip-inno-usb2.c:1148:17: error: 'rk3328_usb2phy_tuning' undeclared here (not in a function)
>    .phy_tuning = rk3328_usb2phy_tuning,
>                  ^
> 
> Caused by commit
> 
>   ffa0c278e89c ("phy: rockchip-inno-usb2: add support of u2phy for rk3328")
> 
> I have used the phy-next tree from next-20170329 for today.

Thanks for reporting this. Will fix it in my tree.

-Kishon