All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	matthew@wil.cx, dwmw2@infradead.org, robert.richter@amd.com,
	gregkh@suse.de, jmorris@namei.org, npiggin@kernel.dk,
	ak@linux.intel.com, dchinner@redhat.com
Subject: Re: [PATCH RFC] fs: introduce a default_open for simple f_op->open use
Date: Mon, 06 Jun 2011 13:36:10 +0300	[thread overview]
Message-ID: <1307356570.3112.31.camel@localhost> (raw)
In-Reply-To: <201106021504.55799.hartleys@visionengravers.com>

On Thu, 2011-06-02 at 15:04 -0700, H Hartley Sweeten wrote:
> There are many f_op->open implementations that simply do:
> 
> 	file->private_data = inode->i_private;
> 
> This introduces a new global symbol, default_open, that can be
> used instead of the private implementations.
> 
> This also removes a couple private implementations that share the
> same symbol name.
> 
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Matthew Wilcox <matthew@wil.cx>
> Cc: Artem Bityutskiy <dedekind1@gmail.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Robert Richter <robert.richter@amd.com>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: James Morris <jmorris@namei.org>
> Cc: Nick Piggin <npiggin@kernel.dk>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Dave Chinner <dchinner@redhat.com>
> 
> ---
> 
> If this patch looks reasonable, I have some additional patches that
> convert all other similar f_op->open implemenations to use default_open
> tree wide.  The full diffstat looks like this:

Looks good to me, thanks.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)


WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	matthew@wil.cx, dwmw2@infradead.org, robert.richter@amd.com,
	gregkh@suse.de, jmorris@namei.org, npiggin@kernel.dk,
	ak@linux.intel.com, dchinner@redhat.com
Subject: Re: [PATCH RFC] fs: introduce a default_open for simple f_op->open use
Date: Mon, 06 Jun 2011 13:36:10 +0300	[thread overview]
Message-ID: <1307356570.3112.31.camel@localhost> (raw)
In-Reply-To: <201106021504.55799.hartleys@visionengravers.com>

On Thu, 2011-06-02 at 15:04 -0700, H Hartley Sweeten wrote:
> There are many f_op->open implementations that simply do:
> 
> 	file->private_data = inode->i_private;
> 
> This introduces a new global symbol, default_open, that can be
> used instead of the private implementations.
> 
> This also removes a couple private implementations that share the
> same symbol name.
> 
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Matthew Wilcox <matthew@wil.cx>
> Cc: Artem Bityutskiy <dedekind1@gmail.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Robert Richter <robert.richter@amd.com>
> Cc: Greg Kroah-Hartman <gregkh@suse.de>
> Cc: James Morris <jmorris@namei.org>
> Cc: Nick Piggin <npiggin@kernel.dk>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Dave Chinner <dchinner@redhat.com>
> 
> ---
> 
> If this patch looks reasonable, I have some additional patches that
> convert all other similar f_op->open implemenations to use default_open
> tree wide.  The full diffstat looks like this:

Looks good to me, thanks.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-06-06 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 22:04 [PATCH RFC] fs: introduce a default_open for simple f_op->open use H Hartley Sweeten
2011-06-06 10:36 ` Artem Bityutskiy [this message]
2011-06-06 10:36   ` Artem Bityutskiy

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=1307356570.3112.31.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=dchinner@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=gregkh@suse.de \
    --cc=hartleys@visionengravers.com \
    --cc=jmorris@namei.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=npiggin@kernel.dk \
    --cc=robert.richter@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.