From: Dave Airlie <firstname.lastname@example.org> To: Stephen Rothwell <email@example.com> Cc: Alan Cox <firstname.lastname@example.org>, Dave Airlie <email@example.com>, firstname.lastname@example.org, email@example.com, Jesse Barnes <firstname.lastname@example.org> Subject: Re: linux-next: build failure after merge of the drm tree Date: Mon, 28 Nov 2011 14:05:13 +0000 Message-ID: <CAPM=9ty_SRGsGaRyDAZbXcdaLXOTapZ2v4J6hyBArfntA8HqDA@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Mon, Nov 28, 2011 at 1:53 PM, Stephen Rothwell <firstname.lastname@example.org> wrote: > Hi Alan, > > On Mon, 28 Nov 2011 13:18:47 +0000 Alan Cox <email@example.com> wrote: >> >> > > Well its very hard to sort stuff out when you are juggling a cross tree >> > > set of dependancies and someone pointlessly stops one of them being >> > > visible in next for ten days. >> > >> > The mess in the drm tree has nothing to do with the staging tree. >> >> I would suggest you re-read the paragraph above, and the mails I sent you >> about marking the staging gma500 tree broken (which given nothing >> happened in response to any of them I imagine you didn't). > > When I originally reported this problem, you responded: > >> gma500 is frozen pending Dave Airlie's applying the patches moving it out >> of staging. >> >> <Prod, prod> > > Which I assumed was aimed at Dave. Then Jesse (whose changes broke the > code in staging) responded with a patch which I assumed that Dave would > do something with. Then the next day you responded with: > >> If the staging gma500 is causing this still please resolve it by marking >> the GMA500 in staging "&& BROKEN" for the moment. > > And maybe I should have done something then. I fall back on the excuse > that I have about 200 trees to merge every day and when I use to fix > things for people I used to have lots of 12-16 hour days ... > >> And if you still think that blocking the DRM tree from -next for ten days >> thus stopping all sorts of other integration work and forcing people's >> hands on moving from staging and the like didn't cause the problems and >> is the right policy then we'll just have to agree to differ. > > If you are trying to get something merged into the drm tree, you should > be working with the drm tree and with the drm maintainer, not > linux-next. Linux-next is here to find integration problems between > trees and across architectures not to find problems with changes within > one tree. > > And I repeat, the breakage today is nothing to do with the staging tree, > it is in the drm tree and how your gma500 changes were merged there (and > to be clear, there is nothing wrong with the gma500 changes per se). > > In the future, I will try to remember to "kill staging first", but this > is the first time it has come up since staging started being built by an > allmodconfig build (which it used not to be - and that change was not my > choice). Yeah I've tracked it down here, I had messed up the configs locally so Alan's code wasn't built, I'll pile some fixes on top of it today. Dave.
next prev parent reply index Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-11-16 0:30 Stephen Rothwell 2011-11-16 10:16 ` Alan Cox 2011-11-16 16:42 ` Jesse Barnes 2011-11-25 1:49 ` Stephen Rothwell 2011-11-25 10:30 ` Alan Cox 2011-11-25 10:34 ` Dave Airlie 2011-11-28 2:53 ` Stephen Rothwell 2011-11-28 11:30 ` Alan Cox 2011-11-28 13:13 ` Stephen Rothwell 2011-11-28 13:18 ` Alan Cox 2011-11-28 13:53 ` Stephen Rothwell 2011-11-28 14:05 ` Dave Airlie [this message] 2011-11-28 14:08 ` Alan Cox 2011-11-28 2:52 ` Stephen Rothwell 2011-11-28 5:07 ` Greg KH 2011-11-28 11:33 ` Alan Cox -- strict thread matches above, loose matches on Subject: below -- 2019-11-05 2:54 Stephen Rothwell 2019-10-10 0:22 Stephen Rothwell 2019-07-08 4:48 Stephen Rothwell 2019-04-26 2:17 Stephen Rothwell 2018-05-16 6:53 Stephen Rothwell 2018-05-16 8:09 ` Oded Gabbay 2018-05-17 5:00 ` Dave Airlie 2018-03-13 5:46 Stephen Rothwell 2018-01-02 1:48 Stephen Rothwell 2017-09-28 4:57 Stephen Rothwell 2017-03-20 0:51 Stephen Rothwell 2017-03-20 8:03 ` Daniel Vetter 2017-03-20 8:05 ` Daniel Vetter 2017-02-23 23:25 Stephen Rothwell 2017-01-24 1:25 Stephen Rothwell 2017-01-25 10:52 ` Vincent ABRIOU 2016-07-15 3:40 Stephen Rothwell 2016-07-15 4:32 ` Sedat Dilek 2016-04-28 1:57 Stephen Rothwell 2016-04-28 8:11 ` Jani Nikula 2016-03-17 4:41 Stephen Rothwell 2016-03-17 8:41 ` Christian König 2016-02-22 0:45 Stephen Rothwell 2015-12-31 10:31 Stephen Rothwell 2016-01-07 2:44 ` Stephen Rothwell 2016-01-11 22:54 ` Stephen Rothwell 2016-01-12 0:31 ` Dave Airlie 2016-01-12 4:35 ` Stephen Rothwell 2016-01-12 7:48 ` Zhu, Rex 2015-12-31 2:40 Stephen Rothwell 2015-12-31 5:14 ` Mark yao 2015-11-04 9:22 Stephen Rothwell 2015-11-09 16:45 ` Guenter Roeck 2015-11-10 4:55 ` Alexandre Courbot 2015-10-06 1:09 Stephen Rothwell 2015-06-09 13:42 Stephen Rothwell 2015-06-09 14:02 ` Deucher, Alexander 2015-06-10 0:28 ` Stephen Rothwell 2015-05-20 3:08 Stephen Rothwell 2015-05-20 4:41 ` Dave Airlie 2015-05-20 5:25 ` Stephen Rothwell 2015-05-20 5:31 ` Stephen Rothwell 2015-05-20 6:01 ` Oded Gabbay 2015-05-20 6:08 ` Dave Airlie 2015-01-29 2:38 Stephen Rothwell 2015-01-29 8:21 ` Oded Gabbay 2015-01-29 9:35 ` Stephen Rothwell 2014-09-08 4:26 Stephen Rothwell 2014-06-05 4:12 Stephen Rothwell 2014-06-05 4:28 ` Stephen Rothwell 2012-09-24 3:18 Stephen Rothwell 2012-09-24 11:31 ` Daniel Vetter 2012-09-24 11:58 ` Stephen Rothwell 2012-08-24 3:49 Stephen Rothwell 2012-05-17 3:47 Stephen Rothwell 2012-04-30 3:22 Stephen Rothwell 2012-04-23 3:42 Stephen Rothwell 2012-03-16 2:53 Stephen Rothwell 2012-03-19 2:45 ` Stephen Rothwell 2011-11-28 2:49 Stephen Rothwell 2011-03-15 3:49 Stephen Rothwell 2010-04-08 3:12 Stephen Rothwell 2010-04-08 3:52 ` Dave Airlie 2010-04-08 4:14 ` Stephen Rothwell 2010-04-08 16:19 ` Tony Luck 2010-04-08 20:50 ` Pauli Nieminen
Reply instructions: You may reply publically 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='CAPM=9ty_SRGsGaRyDAZbXcdaLXOTapZ2v4J6hyBArfntA8HqDA@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
Linux-Next Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \ email@example.com public-inbox-index linux-next Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next AGPL code for this site: git clone https://public-inbox.org/public-inbox.git