From: Greg KH <gregkh@linuxfoundation.org>
To: Janani Ravichandran <janani.rvchndrn@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] staging: lustre: lustre: osc: Modify right hand side of an assignment
Date: Thu, 11 Feb 2016 19:28:29 -0800 [thread overview]
Message-ID: <20160212032829.GA27873@kroah.com> (raw)
In-Reply-To: <20160210064015.GA4712@janani-Inspiron-3521>
On Wed, Feb 10, 2016 at 01:40:15AM -0500, Janani Ravichandran wrote:
> This patch modifies an assignment of the form a = (a <op> b);
> as: a <op>= b; where <op> is << or >>.
> Coccinelle script used:
>
> @@
> identifier i;
> expression e;
> @@
>
> - i = (i >> e);
> + i >>= e;
>
> @@
> identifier i;
> expression e;
> @@
>
> - i = (i << e);
> + i <<= e;
>
> Signed-off-by: Janani Ravichandran <janani.rvchndrn@gmail.com>
> ---
> drivers/staging/lustre/lustre/osc/osc_request.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
The subject line is very "odd", it doesn't say what you are doing.
Well, it does, but it doesn't make much sense.
I understand the changes here, but why are you making them? They aren't
"fixing" anything, nor making the code "simpler" or "cleaner" or
anything else. We don't have any coding style rules that forces someone
to write this type of expression only one way, and I don't want to start
doing that either. So I really don't want to accept patches like this.
Yes, I know I already did, sorry, I'll stop that now. There has to be
lots of other "real" types of fixes / cleanups that you can do instead,
this code needs a lot of work :)
thanks,
greg k-h
prev parent reply other threads:[~2016-02-12 3:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 6:40 [PATCH] staging: lustre: lustre: osc: Modify right hand side of an assignment Janani Ravichandran
2016-02-12 3:28 ` Greg KH [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=20160212032829.GA27873@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=janani.rvchndrn@gmail.com \
--cc=outreachy-kernel@googlegroups.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 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.