From: Joe Perches <joe@perches.com>
To: Albino Biasutti Neto <bino@riseup.net>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Change for codestyle and good read
Date: Wed, 15 Oct 2014 16:26:46 -0700 [thread overview]
Message-ID: <1413415606.7484.19.camel@perches.com> (raw)
In-Reply-To: <1413414942-5338-1-git-send-email-bino@riseup.net>
On Wed, 2014-10-15 at 20:15 -0300, Albino Biasutti Neto wrote:
> ---
Are you not mentioning the logic changes because you
didn't notice them?
> diff --git a/fs/open.c b/fs/open.c
[]
> @@ -71,10 +71,8 @@ long vfs_truncate(struct path *path, loff_t length)
> inode = path->dentry->d_inode;
>
> /* For directories it's -EISDIR, for other non-regulars - -EINVAL */
> - if (S_ISDIR(inode->i_mode))
> + if ((S_ISDIR(inode->i_mode)) && (!S_ISRG(inode->i_mode)))
> return -EISDIR;
> - if (!S_ISREG(inode->i_mode))
> - return -EINVAL;
Don't think so...
Did you read the comment?
> @@ -137,14 +135,13 @@ retry:
> return error;
> }
>
> -SYSCALL_DEFINE2(truncate, const char __user *, path, long, length)
> -{
> +SYSCALL_DEFINE2(truncate, const char __user *, path, long, length) {
> return do_sys_truncate(path, length);
> }
Poorer, non-kernel style
[]
diff --git a/kernel/exit.c b/kernel/exit.c
> index 32c58f7..f429fdd 100644
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -78,8 +78,8 @@ static void __unhash_process(struct task_struct *p, bool group_dead)
> }
>
> /*
> - * This function expects the tasklist_lock write-locked.
> - */
> + * This function expects the tasklist_lock write-locked.
> +*/
> static void __exit_signal(struct task_struct *tsk)
> {
> struct signal_struct *sig = tsk->signal;
Adding trailing whitespace and misaligning too.
next prev parent reply other threads:[~2014-10-15 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 23:15 [PATCH] Change for codestyle and good read Albino Biasutti Neto
2014-10-15 23:26 ` Joe Perches [this message]
2014-10-16 1:55 ` Albino Biasutti Neto
2014-10-16 2:03 ` Joe Perches
2014-10-16 10:14 ` Albino Biasutti Neto
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=1413415606.7484.19.camel@perches.com \
--to=joe@perches.com \
--cc=bino@riseup.net \
--cc=gregkh@linuxfoundation.org \
--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