From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: hch@infradead.org, viro@zeniv.linux.org.uk, adilger@sun.com,
corbet@lwn.net, serue@us.ibm.com, neilb@suse.de,
hooanon05@yahoo.co.jp, bfields@fieldses.org
Cc: linux-fsdevel@vger.kernel.org, sfrench@us.ibm.com,
philippe.deniel@CEA.FR, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/11] exportfs: Return the minimum required handle size
Date: Thu, 03 Jun 2010 21:47:59 +0530 [thread overview]
Message-ID: <87d3w8hyyw.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1275581321-5861-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
I missed a -V13 in the patchset subject. So will resend again with the
current version string so that we get the right patchset when merging
upstream.
-aneesh
next prev parent reply other threads:[~2010-06-03 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 16:08 [PATCH -V13 0/11] Generic name to handle and open by handle syscalls Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 01/11] exportfs: Return the minimum required handle size Aneesh Kumar K.V
2010-06-03 16:17 ` Aneesh Kumar K. V [this message]
2010-06-03 16:08 ` [PATCH 02/11] vfs: Add name to file handle conversion support Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 03/11] vfs: Add open by file handle support Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 04/11] vfs: Allow handle based open on symlinks Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 05/11] vfs: Support null pathname in readlink Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 06/11] ext4: Copy fs UUID to superblock Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 07/11] x86: Add new syscalls for x86_32 Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 08/11] x86: Add new syscalls for x86_64 Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 09/11] ext3: Copy fs UUID to superblock Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 10/11] vfs: Support null pathname in faccessat Aneesh Kumar K.V
2010-06-03 16:08 ` [PATCH 11/11] vfs: Support null pathname in linkat Aneesh Kumar K.V
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=87d3w8hyyw.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=bfields@fieldses.org \
--cc=corbet@lwn.net \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=philippe.deniel@CEA.FR \
--cc=serue@us.ibm.com \
--cc=sfrench@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
/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