All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	kernel-build-reports@lists.linaro.org,
	linaro-kernel@lists.linaro.org, linux-next@vger.kernel.org,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: next-20150604 build: 2 failures 37 warnings (next-20150604)
Date: Thu, 4 Jun 2015 10:10:05 -0700	[thread overview]
Message-ID: <20150604171004.GZ30984@atomide.com> (raw)
In-Reply-To: <20150604170112.GM14071@sirena.org.uk>

* 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.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: next-20150604 build: 2 failures 37 warnings (next-20150604)
Date: Thu, 4 Jun 2015 10:10:05 -0700	[thread overview]
Message-ID: <20150604171004.GZ30984@atomide.com> (raw)
In-Reply-To: <20150604170112.GM14071@sirena.org.uk>

* 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.

Regards,

Tony

  reply	other threads:[~2015-06-04 17:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04 16:47 next-20150604 build: 2 failures 37 warnings (next-20150604) Build bot for Mark Brown
2015-06-04 17:01 ` Mark Brown
2015-06-04 17:01   ` Mark Brown
2015-06-04 17:10   ` Tony Lindgren [this message]
2015-06-04 17:10     ` Tony Lindgren
2015-06-04 17:20     ` Tony Lindgren
2015-06-04 17:20       ` Tony Lindgren
2015-06-04 17:57       ` Mark Brown
2015-06-04 17:57         ` Mark Brown
2015-06-05 10:49       ` Greg Kroah-Hartman
2015-06-05 10:49         ` Greg Kroah-Hartman
2015-06-05 17:16         ` Mark Brown
2015-06-05 17:16           ` Mark Brown
2015-06-08 20:56           ` Greg Kroah-Hartman
2015-06-08 20:56             ` Greg Kroah-Hartman
2015-06-10  7:04             ` Tony Lindgren
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=20150604171004.GZ30984@atomide.com \
    --to=tony@atomide.com \
    --cc=bigeasy@linutronix.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.