From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150604 build: 2 failures 37 warnings (next-20150604)
Date: Fri, 5 Jun 2015 19:49:00 +0900 [thread overview]
Message-ID: <20150605104900.GA5346@kroah.com> (raw)
In-Reply-To: <20150604172026.GA30984@atomide.com>
On Thu, Jun 04, 2015 at 10:20:26AM -0700, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [150604 10:11]:
> > * Mark Brown <broonie@kernel.org> [150604 10:03]:
> > > On Thu, Jun 04, 2015 at 05:47:05PM +0100, Build bot for Mark Brown wrote:
> > >
> > > > arm-allmodconfig
> > > > ../drivers/tty/serial/8250/8250_omap.c:586:20: error: redefinition of 'omap8250_irq'
> > >
> > > Current -next fails to build an ARM allmodconfig (and possibly other
> > > things) due to 9e91597f24234 and 9809889c708eb (serial: 8250_omap:
> > > provide complete custom startup & shutdown callbacks) which appear to be
> > > the same commit that's been applied twice somehow. Not sure what's
> > > going on there...
> >
> > Sounds like I'm using an old commit in one of my pending branches,
> > will check immediately.
>
> Greg, there's now commit 9809889c708e in tty-linus and commit
> 9e91597f2423 in tty-next.
Yes, I can't go back and remove the one in tty-next, I'm guessing when
they are merged there is an issue. I'll look into that after Linus
pulls in my tty-linus tree.
thanks,
greg k-h
next prev parent reply other threads:[~2015-06-05 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Z0YIL-0008Ma-5O@optimist>
2015-06-04 17:01 ` next-20150604 build: 2 failures 37 warnings (next-20150604) Mark Brown
2015-06-04 17:10 ` Tony Lindgren
2015-06-04 17:20 ` Tony Lindgren
2015-06-04 17:57 ` Mark Brown
2015-06-05 10:49 ` Greg Kroah-Hartman [this message]
2015-06-05 17:16 ` Mark Brown
2015-06-08 20:56 ` Greg Kroah-Hartman
2015-06-10 7:04 ` Tony Lindgren
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=20150605104900.GA5346@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).