All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Belisko Marek <marek.belisko@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Sebastian Reichel <sre@kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: Linus HEAD build break
Date: Fri, 6 Nov 2015 06:53:52 -0800	[thread overview]
Message-ID: <20151106145351.GA3218@atomide.com> (raw)
In-Reply-To: <87vb9fyyvn.fsf@saruman.tx.rr.com>

* Felipe Balbi <balbi@ti.com> [151106 06:41]:
> 
> Hi,
> 
> Belisko Marek <marek.belisko@gmail.com> writes:
> > Hi,
> >
> > On Fri, Nov 6, 2015 at 3:24 PM, Felipe Balbi <balbi@ti.com> wrote:
> >>
> >> Hi again,
> >>
> >> Felipe Balbi <balbi@ti.com> writes:
> >>> Hi Marek,
> >>>
> >>> your commit af19161aaed7 ("ARM: dts: twl4030: Add iio properties for bci
> >>> subnode") breaks build on current linus/master (which current sits in
> >>
> >> this commit cannot be found in next. How come it's in linus/master ?
> > I did post fix but Tony seems doesn't merge it:
> > https://lkml.org/lkml/2015/10/13/816
> 
> looking at that thread, I have no idea how come the old version was
> merged in the first place. Tony was clear that it broke build and yet
> this patch has made its way to mainline and it didn't even go through
> linux-next, which makes the problem worse.
> 
> Now we have a bisection point where the tree (well, some DTS files)
> won't even build. This is quite messy.

Yes didn't I drop the patch and pointed out it breaks the build?

Guys, please stop doing this. Do not merge driver code that has
not been sitting in linux next at least a week. And for the dts
changes, please make sure you have proper acks.

And now we have yet another merge window where things unexpectedly
break during the merge window because of untested driver changes.

Please repost the fix and I'll ack it and you guys send a new pull
request to fix it ASAP explaining how it happened.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Linus HEAD build break
Date: Fri, 6 Nov 2015 06:53:52 -0800	[thread overview]
Message-ID: <20151106145351.GA3218@atomide.com> (raw)
In-Reply-To: <87vb9fyyvn.fsf@saruman.tx.rr.com>

* Felipe Balbi <balbi@ti.com> [151106 06:41]:
> 
> Hi,
> 
> Belisko Marek <marek.belisko@gmail.com> writes:
> > Hi,
> >
> > On Fri, Nov 6, 2015 at 3:24 PM, Felipe Balbi <balbi@ti.com> wrote:
> >>
> >> Hi again,
> >>
> >> Felipe Balbi <balbi@ti.com> writes:
> >>> Hi Marek,
> >>>
> >>> your commit af19161aaed7 ("ARM: dts: twl4030: Add iio properties for bci
> >>> subnode") breaks build on current linus/master (which current sits in
> >>
> >> this commit cannot be found in next. How come it's in linus/master ?
> > I did post fix but Tony seems doesn't merge it:
> > https://lkml.org/lkml/2015/10/13/816
> 
> looking at that thread, I have no idea how come the old version was
> merged in the first place. Tony was clear that it broke build and yet
> this patch has made its way to mainline and it didn't even go through
> linux-next, which makes the problem worse.
> 
> Now we have a bisection point where the tree (well, some DTS files)
> won't even build. This is quite messy.

Yes didn't I drop the patch and pointed out it breaks the build?

Guys, please stop doing this. Do not merge driver code that has
not been sitting in linux next at least a week. And for the dts
changes, please make sure you have proper acks.

And now we have yet another merge window where things unexpectedly
break during the merge window because of untested driver changes.

Please repost the fix and I'll ack it and you guys send a new pull
request to fix it ASAP explaining how it happened.

Regards,

Tony

  reply	other threads:[~2015-11-06 14:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 14:06 Linus HEAD build break Felipe Balbi
2015-11-06 14:06 ` Felipe Balbi
2015-11-06 14:24 ` Felipe Balbi
2015-11-06 14:24   ` Felipe Balbi
2015-11-06 14:31   ` Belisko Marek
2015-11-06 14:31     ` Belisko Marek
2015-11-06 14:40     ` Felipe Balbi
2015-11-06 14:40       ` Felipe Balbi
2015-11-06 14:53       ` Tony Lindgren [this message]
2015-11-06 14:53         ` Tony Lindgren
2015-11-06 15:34         ` Sebastian Reichel
2015-11-06 15:34           ` Sebastian Reichel
2015-11-06 16:09           ` Sebastian Reichel
2015-11-06 16:09             ` Sebastian Reichel
2015-11-06 19:03             ` Tony Lindgren
2015-11-06 19:03               ` 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=20151106145351.GA3218@atomide.com \
    --to=tony@atomide.com \
    --cc=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    --cc=sre@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.