6 messages, 4 authors, 2008-07-28 · open the first message on its own page
From: Roland Dreier <hidden>
Date: 2008-07-27 20:34:52
> IMHO, this driver was really rushed in and that was a huge mistake. > If it had gone through linux-next we could have tidied all of this > stuff up in a less "rushed" manner. ?? This thread *is* about a build failure in linux-next. - R.
From: Sam Ravnborg <hidden>
Date: 2008-07-27 20:44:26
On Sun, Jul 27, 2008 at 01:33:49PM -0700, Roland Dreier wrote:
> IMHO, this driver was really rushed in and that was a huge mistake. > If it had gone through linux-next we could have tidied all of this > stuff up in a less "rushed" manner. ?? This thread *is* about a build failure in linux-next.
mISDN are in -linus which is part of -next and Stephens point is that if we have had mISDN in -next then this would have been fixed before hitting -linus. Maybe Karsten should use davem as gateway as he has anyway been so for other isdn patches lately? Sam
From: David Miller <davem@davemloft.net>
Date: 2008-07-27 23:14:42
From: Roland Dreier <redacted> Date: Sun, 27 Jul 2008 13:33:49 -0700
> IMHO, this driver was really rushed in and that was a huge mistake. > If it had gone through linux-next we could have tidied all of this > stuff up in a less "rushed" manner. ?? This thread *is* about a build failure in linux-next.
The driver went directly into Linus's tree. Stephen hit the build problem once he synced linux-next up with Linus's current tree.
From: Stephen Rothwell <hidden>
Date: 2008-07-28 00:16:57
Hi Roland, On Sun, 27 Jul 2008 13:33:49 -0700 Roland Dreier [off-list ref] wrote:
> IMHO, this driver was really rushed in and that was a huge mistake. > If it had gone through linux-next we could have tidied all of this > stuff up in a less "rushed" manner. ?? This thread *is* about a build failure in linux-next.
I noticed this in Linus' tree ... I did not mention linux-next. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Stephen Rothwell <hidden>
Date: 2008-07-28 00:18:12
Hi Sam, On Sun, 27 Jul 2008 22:43:55 +0200 Sam Ravnborg [off-list ref] wrote:
On Sun, Jul 27, 2008 at 01:33:49PM -0700, Roland Dreier wrote:quoted
> IMHO, this driver was really rushed in and that was a huge mistake. > If it had gone through linux-next we could have tidied all of this > stuff up in a less "rushed" manner. ?? This thread *is* about a build failure in linux-next.mISDN are in -linus which is part of -next and Stephens point is that if we have had mISDN in -next then this would have been fixed before hitting -linus.
Dave made that point, not me. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/
From: Stephen Rothwell <hidden>
Date: 2008-07-28 00:20:53
Hi Dave, On Sun, 27 Jul 2008 16:14:32 -0700 (PDT) David Miller [off-list ref] wrote:
The driver went directly into Linus's tree. Stephen hit the build problem once he synced linux-next up with Linus's current tree.
It didn't even get as far as linux-next, I was just browsing the bloodbath that is/was Linus' tree (http://kisskb.ellerman.id.au/kisskb/branch/3/) :-(. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/