From: "J.H." <warthog9@kernel.org>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
Nick Piggin <npiggin@gmail.com>,
patchwork@lists.ozlabs.org, Al Viro <viro@zeniv.linux.org.uk>,
"J. R. Okajima" <hooanon05@yahoo.co.jp>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: vfs-scale, nd->inode after __do_follow_link()
Date: Fri, 14 Jan 2011 15:34:04 -0800 [thread overview]
Message-ID: <4D30DD6C.4010507@kernel.org> (raw)
In-Reply-To: <AANLkTik=7x9o3s_TeVAACjNachLE7zyrbqyOeBBiE-v5@mail.gmail.com>
> [ 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@kernel.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
next prev parent reply other threads:[~2011-01-14 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 2:10 vfs-scale, nd->inode after __do_follow_link() J. R. Okajima
2011-01-14 2:33 ` J. R. Okajima
2011-01-14 4:09 ` Nick Piggin
2011-01-14 4:41 ` J. R. Okajima
2011-01-14 5:28 ` Al Viro
2011-01-14 5:38 ` J. R. Okajima
2011-01-14 5:40 ` J. R. Okajima
2011-01-14 8:40 ` Nick Piggin
2011-01-14 9:17 ` Sedat Dilek
2011-01-14 23:34 ` J.H. [this message]
2011-01-14 12:54 ` J. R. Okajima
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=4D30DD6C.4010507@kernel.org \
--to=warthog9@kernel.org \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=patchwork@lists.ozlabs.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=webmaster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).