linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: "Chuck Lever" <chucklever@gmail.com>
Cc: "David Howells" <dhowells@redhat.com>,
	torvalds@osdl.org, akpm@osdl.org, steved@redhat.com,
	trond.myklebust@fys.uio.no, linux-fsdevel@vger.kernel.org,
	linux-cachefs@redhat.com, nfsv4@linux-nfs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] NFS: Use local caching [try #12]
Date: Fri, 18 Aug 2006 16:51:06 +0100	[thread overview]
Message-ID: <30101.1155916266@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <76bd70e30608180843m536e9f57y90e1915f40f85b2@mail.gmail.com>

Chuck Lever <chucklever@gmail.com> wrote:

> > +static uint16_t nfs_server_get_key(const void *cookie_netfs_data,
> > +                                  void *buffer, uint16_t bufmax)
> > +{
> 
> Why don't you use the function declaration style that is used in the
> rest of the NFS client?

Actually, the NFS client has several different styles, and mine's not without
precedent, eg:

extern int nfs3_setxattr(struct dentry *, const char *,
			const void *, size_t, int);

extern ssize_t nfs_direct_IO(int, struct kiocb *, const struct iovec *, loff_t,
			unsigned long);

static inline loff_t
nfs_size_to_loff_t(__u64 size)

> All the parameters belong on one line, don't they?

Depends how much you want to upset those people who tremble with anxiety at
the sight of a line longer than 80 chars.

David

  parent reply	other threads:[~2006-08-18 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 15:35 [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #12] David Howells
2006-08-18 15:35 ` [PATCH 1/7] FS-Cache: Provide a filesystem-specific sync'able page bit " David Howells
2006-08-18 15:35 ` [PATCH 2/7] FS-Cache: Generic filesystem caching facility " David Howells
2006-08-18 15:35 ` [PATCH 3/7] FS-Cache: Release page->private after failed readahead " David Howells
2006-08-18 15:35 ` [PATCH 4/7] FS-Cache: Make kAFS use FS-Cache " David Howells
2006-08-18 15:35 ` [PATCH 5/7] NFS: Use local caching " David Howells
2006-08-18 15:43   ` Chuck Lever
2006-08-18 18:41     ` Jeff Garzik
2006-08-18 15:51   ` David Howells [this message]
2006-08-18 15:35 ` [PATCH 6/7] FS-Cache: CacheFiles: ia64: missing copy_page export " David Howells
2006-08-18 15:35 ` [PATCH 7/7] FS-Cache: CacheFiles: A cache that backs onto a mounted filesystem " David Howells

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=30101.1155916266@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=chucklever@gmail.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=steved@redhat.com \
    --cc=torvalds@osdl.org \
    --cc=trond.myklebust@fys.uio.no \
    /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).