mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	bfields@fieldses.org, ebiederm@xmission.com, neilb@suse.de
Subject: Re: + nfsd-use-proc_create-to-setup-de-proc_fops.patch added to -mm tree
Date: Sun, 20 Apr 2008 22:48:48 +0400	[thread overview]
Message-ID: <20080420184848.GA31337@martell.zuzino.mipt.ru> (raw)
In-Reply-To: <1208708509.14894.3.camel@iris.sw.ru>

On Sun, Apr 20, 2008 at 08:21:49PM +0400, Denis V. Lunev wrote:
> 
> On Sun, 2008-04-20 at 18:37 +0400, Alexey Dobriyan wrote:
> > On Tue, Apr 15, 2008 at 04:55:57PM -0700, akpm@linux-foundation.org wrote:
> > > --- a/fs/nfsd/nfsctl.c~nfsd-use-proc_create-to-setup-de-proc_fops
> > > +++ a/fs/nfsd/nfsctl.c
> > 
> > > @@ -736,10 +737,9 @@ static int create_proc_exports_entry(voi
> > >  	entry = proc_mkdir("fs/nfs", NULL);
> > >  	if (!entry)
> > >  		return -ENOMEM;
> > > -	entry = create_proc_entry("fs/nfs/exports", 0, NULL);
> > > +	entry = proc_create("exports", 0, entry, &exports_operations);
> > 			    ^^^^^^^^^
>                                            ^^^^^^^
> > >  	if (!entry)
> > >  		return -ENOMEM;
> > > -	entry->proc_fops =  &exports_operations;
> > 
> > "fs/nfs/exports" is used in full in this file. And line will fit into
> > 80 columns.
> > 
> This is a pde for fs/nfs.

Yes, why change it?

> So, this will be slightly less operations in my case.

It's done once per module loading, so nobody cares.


      reply	other threads:[~2008-04-20 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804152355.m3FNtv3O022485@imap1.linux-foundation.org>
2008-04-20 14:37 ` Alexey Dobriyan
2008-04-20 16:21   ` Denis V. Lunev
2008-04-20 18:48     ` Alexey Dobriyan [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=20080420184848.GA31337@martell.zuzino.mipt.ru \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bfields@fieldses.org \
    --cc=den@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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

all inboxes | Powered by JetHome®