public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: David Howells <dhowells@warthog.cambridge.redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	David Howells <dhowells@redhat.com>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, openafs-devel@openafs.org
Subject: Re: [PATCH] PAG support only
Date: Wed, 14 May 2003 09:39:44 +0100	[thread overview]
Message-ID: <20030514093944.A9474@infradead.org> (raw)
In-Reply-To: <13536.1052900263@warthog.warthog>; from dhowells@warthog.cambridge.redhat.com on Wed, May 14, 2003 at 09:17:43AM +0100

On Wed, May 14, 2003 at 09:17:43AM +0100, David Howells wrote:
> > - and even a wrong one..
> 
> I disagree, but no matter.

It's not a matter of your (or my) personal opinion of coding style.  Linux
is a big project and it's only maintainable if everyone sticks to a slightly
similar style.  


> > > +static kmem_cache_t *vfs_token_cache;
> > > +static kmem_cache_t *vfs_pag_cache;
> > 
> > How many of those will be around for a typical AFS client?  I have the vague
> > feeling the slabs are overkill..
> 
> And then there's the people who said I shouldn't use kmalloc but should create
> a slab instead...

That's why I ask how much it is used.  Could you answer the question maybe?

> 
> > > +	if (pag>0) {
> > > +		/* join existing PAG */
> > > +		if (tsk->vfspag->pag &&
> > > +		    tsk->vfspag->pag==pag)
> > > +			return pag;
> > 
> > Please try to get your code in conformance with Documentation/CodingStyle.
> 
> You are suggesting what changes exactly?

spaces between operators to start with.  It's not that difficult to read the
above document and other core kernel code, though.


  reply	other threads:[~2003-05-14  8:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 16:33 [PATCH] PAG support only David Howells
2003-05-13 16:48 ` Jeff Garzik
2003-05-13 20:37 ` Christoph Hellwig
2003-05-13 22:27   ` [OpenAFS-devel] " Nathan Neulinger
2003-05-14  5:33     ` Christoph Hellwig
2003-05-16 15:24     ` Derek Atkins
2003-05-14  8:17   ` David Howells
2003-05-14  8:39     ` Christoph Hellwig [this message]
2003-05-14  4:57 ` Muli Ben-Yehuda
2003-05-14  9:54   ` David Howells
2003-05-14 12:35     ` Muli Ben-Yehuda
2003-05-14 13:17       ` David Howells
     [not found] <20030513175240.6313ea92.akpm@digeo.com>
2003-05-14  9:44 ` David Howells
2003-05-14 10:00   ` Andrew Morton
2003-05-14 10:01   ` Miles Bader
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 16:04 Chuck Ebbert
2003-05-14 16:20 ` William Lee Irwin III

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=20030514093944.A9474@infradead.org \
    --to=hch@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=dhowells@warthog.cambridge.redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openafs-devel@openafs.org \
    --cc=torvalds@transmeta.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