From: Greg KH <gregkh@linuxfoundation.org>
To: Yan Hong <clouds.yan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] debugfs: break long lines
Date: Fri, 26 Oct 2012 11:12:38 -0700 [thread overview]
Message-ID: <20121026181238.GB25530@kroah.com> (raw)
In-Reply-To: <1351274144-31591-3-git-send-email-clouds.yan@gmail.com>
On Sat, Oct 27, 2012 at 01:55:44AM +0800, Yan Hong wrote:
>
> Signed-off-by: Yan Hong <clouds.yan@gmail.com>
> ---
> fs/debugfs/file.c | 42 ++++++++++++++++++++++++++++--------------
> fs/debugfs/inode.c | 10 ++++++----
> 2 files changed, 34 insertions(+), 18 deletions(-)
>
> diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> index 3915cc9..b37eee1 100644
> --- a/fs/debugfs/file.c
> +++ b/fs/debugfs/file.c
> @@ -95,10 +95,12 @@ struct dentry *debugfs_create_u8(const char *name, umode_t mode,
> {
> /* if there are no write bits set, make read only */
> if (!(mode & S_IWUGO))
> - return debugfs_create_file(name, mode, parent, value, &fops_u8_ro);
> + return debugfs_create_file(name, mode, parent, value,
> + &fops_u8_ro);
If you are going to do this (and hint, I really don't want you to), at
least make it look pretty:
return debugfs_create_file(name, mode, parent, value,
&fops_u8_ro);
Other than that, I don't want to take this patch, sorry, it looks good
enough as-is.
thanks,
greg k-h
next prev parent reply other threads:[~2012-10-26 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 17:55 [PATCH 1/3] debugfs: pass NULL as the last parameter of debugfs_print_regs32() Yan Hong
2012-10-26 17:55 ` [PATCH 2/3] debugfs: code clean and refactor Yan Hong
2012-10-26 18:12 ` Greg KH
2012-10-26 17:55 ` [PATCH 3/3] debugfs: break long lines Yan Hong
2012-10-26 18:12 ` Greg KH [this message]
2012-10-26 18:13 ` [PATCH 1/3] debugfs: pass NULL as the last parameter of debugfs_print_regs32() Greg KH
2012-10-26 18:34 ` yan yan
2012-10-26 18:48 ` Greg KH
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=20121026181238.GB25530@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=clouds.yan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome