mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Pranith Kumar <pranith.hacks@gmail.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [TRIVIAL][PATCH 1/1] Fix warning in staging/otus/ioctl.c
Date: Mon, 08 Jun 2009 20:18:16 +0200	[thread overview]
Message-ID: <4A2D55E8.3070900@s5r6.in-berlin.de> (raw)
In-Reply-To: <4A2D51E6.6030607@s5r6.in-berlin.de>

I wrote:
> However, the code which you looked 
> at also has other trivial deviations from kernel style.  Notably, the 
> use of CamelCase names rather than all-lowercase with underscores. 

PS:  Name changes are already at least one level more difficult than 1:1 
type replacements, because giving _good_ names to variables/ functions 
etc. requires deeper understanding of what the code does.

> if you are interested in doing that, then you can plan ahead and hold
> off with whitespace adjusting changes (indentation, line wraps...)
> until after you did those other changes

But that's only an 'if'.  If you rather only want to work on a single 
logical step for now, e.g. type replacement, then that's surely very 
welcome too.  (My only concern about the "Fix warning..." was that 
making the warnings go away does not lead to actual improvements, or 
worse, covers up actual issues with the code.  I.e. I didn't want to 
press you in to fixing those, just to take care _not_ to paper over them.)
-- 
Stefan Richter
-=====-==--= -==- -=---
http://arcgraph.de/sr/

  reply	other threads:[~2009-06-08 18:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:19 Pranith Kumar
2009-06-08  8:08 ` Pranith Kumar
2009-06-08  9:09   ` Stefan Richter
2009-06-08 10:02     ` Pranith Kumar
2009-06-08 18:01       ` Stefan Richter
2009-06-08 18:18         ` Stefan Richter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-29  7:54 Pranith Kumar
2009-06-02 21:47 ` Greg KH
2009-06-03  6:49   ` Pranith Kumar
2009-06-03 15:21     ` Greg KH
2009-06-04  5:53       ` Pranith Kumar
2009-06-04 17:56         ` Greg KH
2009-06-05  5:10           ` Pranith Kumar
2009-06-05  6:15             ` Pranith Kumar
2009-06-04 18:37         ` Miguel Ojeda

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=4A2D55E8.3070900@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pranith.hacks@gmail.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®