[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D30DD6C.4010507@kernel.org>
Date: Fri, 14 Jan 2011 15:34:04 -0800
From: "J.H." <warthog9@...nel.org>
To: sedat.dilek@...il.com
CC: Sedat Dilek <sedat.dilek@...glemail.com>,
Nick Piggin <npiggin@...il.com>, patchwork@...ts.ozlabs.org,
Al Viro <viro@...iv.linux.org.uk>,
"J. R. Okajima" <hooanon05@...oo.co.jp>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel@...r.kernel.org, webmaster@...nel.org
Subject: Re: vfs-scale, nd->inode after __do_follow_link()
> [ CCing patchwork ML ]
>
> Can you send your patch separately, please?
> Within a (long) thread it is eaten up.
>
> As *.patch are somehow not presented as diff (see [1]), someone can't
> catch them from <patchwork.k.o>.
On a side note, due to some conversations with the ocfs2 devs yesterday,
I've actually got the vfs-scale code sitting compiled up waiting for
another kernel panic to happen on the dynamic web boxes, since 2.6.37+
was, literally, unusable with ocfs2 running.
> Furthermore, it would be very cool to see linux-fsdevel (patches from
> its ML) in <patchwork.d.o>.
> I don't know whom to contact from the linux-fsdevel ML, sorry for this.
As to getting a mailing list added into patchwork.kernel.org I just need
a request from someone who is responsible for the mailing list, and who
will actually use the resulting entry in patchwork to e-mail
ftpadmin@...nel.org with the mailing list, where I can deal with the
sign-up and the name / username of the individual (in patchwork) to add
as being in charge.
- John 'Warthog9' Hawley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists