From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the mfd-lj tree
Date: Mon, 3 Mar 2014 15:23:31 +0800 [thread overview]
Message-ID: <20140303072331.GB4674@lee--X1> (raw)
In-Reply-To: <20140303161803.ecbd9b124b5f2cdf79b8cf51@canb.auug.org.au>
Hi Stephen,
> > > > > 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.)
Sorry about all this. Your mails are being filtered into an unused
mailbox for a currently unknown reason. I will investigate this
immediately. It was a mistake to push this patch, I will rectify right
away.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-03 7:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 2:42 linux-next: build failure after merge of the mfd-lj tree Stephen Rothwell
2014-02-17 3:14 ` Stephen Rothwell
2014-02-20 4:05 ` Stephen Rothwell
2014-02-25 3:32 ` Stephen Rothwell
2014-03-03 5:18 ` Stephen Rothwell
2014-03-03 7:23 ` Lee Jones [this message]
2014-03-03 7:37 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 5:20 Stephen Rothwell
2014-05-20 8:01 Stephen Rothwell
2014-05-22 22:15 ` Linus Walleij
2014-04-24 3:01 Stephen Rothwell
2014-02-11 2:25 Stephen Rothwell
2014-03-04 3:03 ` Stephen Rothwell
2014-03-04 7:05 ` Lee Jones
2014-03-04 8:06 ` Lee Jones
2014-03-04 23:36 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140303072331.GB4674@lee--X1 \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).