From: Tony Lindgren <tony@atomide.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Mark Brown <broonie@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
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: Wed, 10 Jun 2015 00:04:02 -0700 [thread overview]
Message-ID: <20150610070402.GB2740@atomide.com> (raw)
In-Reply-To: <20150608205632.GB11211@kroah.com>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> [150608 13:58]:
> On Fri, Jun 05, 2015 at 06:16:52PM +0100, Mark Brown wrote:
> > On Fri, Jun 05, 2015 at 07:49:00PM +0900, Greg Kroah-Hartman wrote:
> > > On Thu, Jun 04, 2015 at 10:20:26AM -0700, Tony Lindgren wrote:
> >
> > > > 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.
> >
> > Yeah, git isn't always spectacularly good at resolving add/add if
> > there's context changes between two things in a merge - it sometimes
> > ends up double adding things.
>
> Ok, I've now merged these branches together, if someone can verify that
> my tty-next branch is correct, that would be great.
I've verified that things are working for 8250_omap thanks.
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: Wed, 10 Jun 2015 00:04:02 -0700 [thread overview]
Message-ID: <20150610070402.GB2740@atomide.com> (raw)
In-Reply-To: <20150608205632.GB11211@kroah.com>
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> [150608 13:58]:
> On Fri, Jun 05, 2015 at 06:16:52PM +0100, Mark Brown wrote:
> > On Fri, Jun 05, 2015 at 07:49:00PM +0900, Greg Kroah-Hartman wrote:
> > > On Thu, Jun 04, 2015 at 10:20:26AM -0700, Tony Lindgren wrote:
> >
> > > > 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.
> >
> > Yeah, git isn't always spectacularly good at resolving add/add if
> > there's context changes between two things in a merge - it sometimes
> > ends up double adding things.
>
> Ok, I've now merged these branches together, if someone can verify that
> my tty-next branch is correct, that would be great.
I've verified that things are working for 8250_omap thanks.
Tony
next prev parent reply other threads:[~2015-06-10 7:04 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
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 [this message]
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=20150610070402.GB2740@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.