From: "Drokin, Oleg" <oleg.drokin@intel.com>
To: "Abdul, Hussain (H.)" <habdul@visteon.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
"HPDD-discuss@lists.01.org" <HPDD-discuss@ml01.01.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ravindran, Madhusudhanan (M.)" <mravindr@visteon.com>,
"Dighe, Niranjan (N.)" <ndighe@visteon.com>
Subject: Re: [PATCH] Staging: lusture: Remove an open coded simple_open() function
Date: Tue, 16 Jun 2015 07:07:38 +0000 [thread overview]
Message-ID: <14E04FD4-9283-406C-A5D2-68B27DF58F5F@intel.com> (raw)
In-Reply-To: <1434438105-4648-1-git-send-email-habdul@visteon.com>
On Jun 16, 2015, at 3:03 AM, Abdul, Hussain (H.) wrote:
> From: Abdul Hussain <habdul@visteon.com>
>
> This patch removes an open coded simple_open() function and replace file
> operations references to the function with simple_open() instead
>
> Signed-off-by: Abdul Hussain <habdul@visteon.com>
> ---
> drivers/staging/lustre/lustre/fld/lproc_fld.c | 9 +--------
> 1 file changed, 1 insertion(+), 8 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/fld/lproc_fld.c b/drivers/staging/lustre/lustre/fld/lproc_fld.c
> index b35ff28..d19b724 100644
> --- a/drivers/staging/lustre/lustre/fld/lproc_fld.c
> +++ b/drivers/staging/lustre/lustre/fld/lproc_fld.c
> @@ -143,13 +143,6 @@ fld_debugfs_cache_flush_write(struct file *file, const char __user *buffer,
> }
>
> static int
> -fld_debugfs_cache_flush_open(struct inode *inode, struct file *file)
> -{
> - file->private_data = inode->i_private;
> - return 0;
> -}
> -
> -static int
> fld_debugfs_cache_flush_release(struct inode *inode, struct file *file)
> {
> file->private_data = NULL;
> @@ -158,7 +151,7 @@ fld_debugfs_cache_flush_release(struct inode *inode, struct file *file)
>
> static struct file_operations fld_debugfs_cache_flush_fops = {
> .owner = THIS_MODULE,
> - .open = fld_debugfs_cache_flush_open,
> + .open = simple_open,
Could you please save the indenting to match the rest of this structure assignment?
> .write = fld_debugfs_cache_flush_write,
> .release = fld_debugfs_cache_flush_release,
> };
> --
> 1.9.1
prev parent reply other threads:[~2015-06-16 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 7:03 Abdul, Hussain (H.)
2015-06-16 7:07 ` Drokin, Oleg [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=14E04FD4-9283-406C-A5D2-68B27DF58F5F@intel.com \
--to=oleg.drokin@intel.com \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=habdul@visteon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mravindr@visteon.com \
--cc=ndighe@visteon.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
all inboxes | Powered by JetHome®