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:   Wed, 18 Nov 2020 09:53:58 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Kishon Vijay Abraham I <kishon@...com>,
        Yejune Deng <yejune.deng@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the phy-next tree

On 18-11-20, 13:56, Stephen Rothwell wrote:
> Hi Vinod,
> 
> On Tue, 17 Nov 2020 15:30:56 +0530 Vinod Koul <vkoul@...nel.org> wrote:
> >
> > On 17-11-20, 13:40, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > After merging the phy-next tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:
> > > 
> > > drivers/soc/amlogic/meson-ee-pwrc.c: In function 'meson_ee_pwrc_init_domain':
> > > drivers/soc/amlogic/meson-ee-pwrc.c:416:65: error: expected ';' before 'if'
> > >   416 |   dom->rstc = devm_reset_control_array_get_exclusive(&pdev->dev)
> > >       |                                                                 ^
> > >       |                                                                 ;
> > >   417 |   if (IS_ERR(dom->rstc))
> > >       |   ~~                                                             
> > > 
> > > Caused by commit
> > > 
> > >   3cc8e86721ad ("phy: amlogic: Replace devm_reset_control_array_get()")
> > > 
> > > I have used the phy-next tree from next-20201116 for today.  
> > 
> > I have reverted this commit
> 
> Thanks, but forgot to push out?

Precisely :( Fixed now, sorry for the trouble

-- 
~Vinod

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ