linux-kernel - Re: linux-next: build failure after merge of the mfd-lj 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:	Mon, 3 Mar 2014 16:18:03 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Lee Jones <lee.jones@...aro.org>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the mfd-lj tree

Hi Lee,

On Tue, 25 Feb 2014 14:32:46 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Thu, 20 Feb 2014 15:05:08 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > On Mon, 17 Feb 2014 14:14:46 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > >
> > > On Fri, 14 Feb 2014 13:42:17 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > > >
> > > > After merging the mfd-lj tree, today's linux-next build (x86_64
> > > > allmodconfig) failed like this:
> > > > 
> > > > In file included from drivers/mfd/max665x.c:19:0:
> > > > include/linux/mfd/max665x-private.h:31:1: error: expected ';', identifier or '(' before 'struct'
> > > >  struct max665x_dev {
> > > >  ^
> > > > 
> > > > Caused by commit e77bb5297293 ("mfd: max665x: Differentiate between
> > > > MAX665X devices").  Clearly never built by anyone :-(
> > > > 
> > > > I have used the mfd-lj tree from next-20140210 again for today (since the
> > > > other version had other problems).
> > > 
> > > Still seeing this error.
> > 
> > Still ...
> 
> Ping ...

I am still seeing this error which means that I am still using the
version of your tree from next-20140210 i.e. Feb 10.  It is a bit
disappointing that his has not been fixed in such a long time even though
there have been other updates to your tree which means that those other
changes have received no exposure in linux-next.  It is a trivial error,
but it does indicate that noone ever build tested that particular commit.

(this is now commit 2fc7e7d25bee in your tree since it was rewritten but
not fixed on Feb 14.)

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

Content of type "application/pgp-signature" skipped