From: Chihau Chau <chihau@gmail.com>
To: James Kosin <jkosin@intcomgrp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Security: key: keyring: fix some code style issues
Date: Tue, 9 Mar 2010 15:50:17 -0300 [thread overview]
Message-ID: <f5ca57691003091050l8589a5al7ee3dfef78432e35@mail.gmail.com> (raw)
In-Reply-To: <4B969026.8040106@intcomgrp.com>
Now I understand. Sorry for my little confusion.
I am making a new patch.
Thanks!
2010/3/9 James Kosin <jkosin@intcomgrp.com>:
> On 3/9/2010 12:39 PM, Chihau Chau wrote:
> Chau,
>
> Below is your original patch set.
>
> From: Chihau Chau <chihau@gmail.com>
>
> This fixes some code style issues like to include <linux/uaccess.h> instead
> <asm/uaccess.h> and to remove some innecessary braces.
>
> Signed-off-by: Chihau Chau <chihau@gmail.com>
> ---
> security/keys/keyring.c | 11 ++++-------
> 1 files changed, 4 insertions(+), 7 deletions(-)
>
> diff --git a/security/keys/keyring.c b/security/keys/keyring.c
> index e814d21..5a44965 100644
> --- a/security/keys/keyring.c
> +++ b/security/keys/keyring.c
> @@ -17,7 +17,7 @@
> #include <linux/seq_file.h>
> #include <linux/err.h>
> #include <keys/keyring-type.h>
> -#include <asm/uaccess.h>
> +#include <linux/uaccess.h>
> #include "internal.h"
>
> /*
> @@ -170,12 +170,10 @@ static void keyring_describe(const struct key
> *keyring, struct seq_file *m)
> {
> struct keyring_list *klist;
>
> - if (keyring->description) {
> + if (keyring->description)
> seq_puts(m, keyring->description);
> - }
> - else {
> + else
> seq_puts(m, "[anon]");
> - }
>
>
> Here is where I said NOT to remove the braces. However you can see the
> style of the if() {} else {} blocks is not the same as below where you point
> to the style of the statements as to the reason for the change.
>
>
> rcu_read_lock();
> klist = rcu_dereference(keyring->payload.subscriptions);
> @@ -775,8 +773,7 @@ int __key_link(struct key *keyring, struct key *key)
> smp_wmb();
> klist->nkeys++;
> smp_wmb();
> - }
> - else {
> + } else {
> /* grow the key list */
> max = 4;
>
>
> See HERE.
>
> if (klist)
> --
> 1.5.6.3
>
> One of these is wrong. Check the coding style document as to which is
> correct.
>
> Sorry to be so critical.
>
> Regards,
> James K.
>
--
Chihau Chau
next prev parent reply other threads:[~2010-03-09 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <elUoX-6na-35@gated-at.bofh.it>
2010-03-09 16:44 ` [PATCH] Security: key: keyring: fix some code style issues James Kosin
2010-03-09 17:01 ` Chihau Chau
[not found] ` <4B9683CF.5040402@intcomgrp.com>
2010-03-09 17:39 ` Chihau Chau
[not found] ` <4B969026.8040106@intcomgrp.com>
2010-03-09 18:50 ` Chihau Chau [this message]
2010-03-08 23:11 Chihau Chau
2010-03-09 21:25 ` David Howells
2010-03-09 21:47 ` James Morris
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=f5ca57691003091050l8589a5al7ee3dfef78432e35@mail.gmail.com \
--to=chihau@gmail.com \
--cc=jkosin@intcomgrp.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;
as well as URLs for NNTP newsgroup(s).