From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>
Cc: Ted Ts'o <tytso@mit.edu>, Eric Sandeen <sandeen@redhat.com>,
Bernd Schubert <bernd.schubert@fastmail.fm>,
linux-nfs@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, yong.fan@whamcloud.com,
adilger@whamcloud.com, "J. Bruce Fields" <bfields@redhat.com>
Subject: Re: [PATCH 0/4] 32/64 bit llseek hashes (v4)
Date: Thu, 8 Dec 2011 16:10:36 -0500 [thread overview]
Message-ID: <20111208211036.GE32505@fieldses.org> (raw)
In-Reply-To: <4EE0FF93.9060907@itwm.fraunhofer.de>
On Thu, Dec 08, 2011 at 07:18:59PM +0100, Bernd Schubert wrote:
> Ted,
>
> is there anything I can do to get those patched into 3.3?
> The patches still apply in current linux-git.
They appear to solve a real problem for nfsd. What's holding them up?
--b.
prev parent reply other threads:[~2011-12-08 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 9:57 [PATCH 0/4] 32/64 bit llseek hashes (v4) Bernd Schubert
2011-08-17 9:57 ` [PATCH 4 1/4] Add new FMODE flags: FMODE_32bithash and FMODE_64bithash Bernd Schubert
2011-08-17 9:57 ` [PATCH 4 2/4] Return 32/64-bit dir name hash according to usage type Bernd Schubert
2011-08-17 9:57 ` [PATCH 4 3/4] nfsd_open(): rename 'int access' to 'int may_flags' in nfsd_open() Bernd Schubert
2011-08-17 9:57 ` [PATCH 4 4/4] nfsd: vfs_llseek() with 32 or 64 bit offsets (hashes) Bernd Schubert
2011-08-30 22:12 ` [PATCH 0/4] 32/64 bit llseek hashes (v4) Bernd Schubert
[not found] ` <4E5D6058.8040805-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2011-11-09 14:59 ` Eric Sandeen
2011-12-08 18:18 ` Bernd Schubert
2011-12-08 21:10 ` J. Bruce Fields [this message]
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=20111208211036.GE32505@fieldses.org \
--to=bfields@fieldses.org \
--cc=adilger@whamcloud.com \
--cc=bernd.schubert@fastmail.fm \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=bfields@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
--cc=yong.fan@whamcloud.com \
/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).