Messages in this thread | | | Date | Wed, 29 Jul 2009 00:49:41 +0100 | From | Alan Cox <> | Subject | Re: [PATCH] kdesu broken |
| |
On Tue, 28 Jul 2009 18:02:03 -0400 Theodore Tso <tytso@mit.edu> wrote:
> On Tue, Jul 28, 2009 at 02:01:21PM -0700, Greg KH wrote: > > On Tue, Jul 28, 2009 at 04:47:20PM -0400, Theodore Tso wrote: > > > On Tue, Jul 28, 2009 at 12:56:48PM -0700, Greg KH wrote: > > > > > > > > Do you have a pointer to your previous queue before you zapped it so > > > > that others might be able to pick it up? > > > > > > > > > > It's also available from linux-next as commit: > > > > > > 024ea7873598686f3e02002ca23c2e8fa3fddd30 > > > > Hm, that's the wrong end of the tree, I think you mean > > fbfa97a856a4ce2fa86058cff84f589eb7f1364e, right? > > It all depends on your point of view, I guess. The "last" commit in > the branch is 024ea78, so you can see the whole queue if you use the > command "git log 024ea78"; hence, it's the most useful if you're > trying to find the patch series via git. > > The whole set of tty patches can be found via: > > git log e00b95d..024ea78 > > (where e00b95d is the parent of fbfa978).
I'll fish them out tomorrow. What is in the -next tree is only some of the bits.
We still have races on the USB side too btw I put a frequency generator on the carrier line of my pl2303 with an app continually opening the port and it oopses after about 10 minutes. On the bright side so does 2.6.29, 2.6.27 ....
Alan
| |