netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 4/6] phy: kill excess code
Date: Sat, 04 Jan 2014 19:24:19 +0300	[thread overview]
Message-ID: <52C835B3.80103@cogentembedded.com> (raw)
In-Reply-To: <CAGVrzcadLFE-FWvgDQE5gkd6COZkGs2Q4SQdnOdKE4Deu-qa0A@mail.gmail.com>

Hello.

On 01/04/2014 01:12 PM, Florian Fainelli wrote:

>  > Remove tens of lines of unnecessary code:

>  > - kill empty lines between a function call and its result check;

>  > - convert assignments to initializers;

>  > - kill useless assignments before *return*;

>  > - kill excess empty lines.

> I might be completely out of date on what checkpatch is picky about these days

    Yes, you probably are.

> but it seems to me like all of these changes would trigger new warnings, I

    No new warnings were added. You should really have checked before you 
spoken out.

> will take a closer look, but for now I don't see this patch making any
> reability improvements, quite the contrary.

    Apparently, tastes vary. To me, e.g. empty lines between the function call 
and result (error) check are a waste of space which is avoided by all other 
kernel code I had to read.

>  > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com
> <mailto:sergei.shtylyov@cogentembedded.com>>

>  > ---
>  >  drivers/net/phy/phy.c        |   31 ++++------------------------
>  >  drivers/net/phy/phy_device.c |   46
> +++++++------------------------------------
>  >  2 files changed, 13 insertions(+), 64 deletions(-)

    May I ask you not to quote the full patch if you're replying only to the 
header? Please show some respect to people who read your messages.

WBR, Sergei

  parent reply	other threads:[~2014-01-04 15:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04  1:13 [PATCH 0/6] phylib: cleanups Sergei Shtylyov
2014-01-04  1:14 ` [PATCH 1/6] phy: coding style fixes Sergei Shtylyov
2014-01-04  1:16 ` [PATCH 2/6] mdio_bus: " Sergei Shtylyov
2014-01-04  1:17 ` [PATCH 3/6] phy: kill useless local variables Sergei Shtylyov
2014-01-04  7:34   ` Richard Cochran
2014-01-04  1:19 ` [PATCH 4/6] phy: kill excess code Sergei Shtylyov
2014-01-04  7:36   ` Richard Cochran
2014-01-04 16:29     ` Sergei Shtylyov
2014-01-04 15:42       ` Richard Cochran
2014-01-04 16:47         ` Sergei Shtylyov
2014-01-04 15:51           ` Richard Cochran
2014-01-05  0:50             ` Sergei Shtylyov
     [not found]   ` <CAGVrzcadLFE-FWvgDQE5gkd6COZkGs2Q4SQdnOdKE4Deu-qa0A@mail.gmail.com>
2014-01-04 16:24     ` Sergei Shtylyov [this message]
2014-01-04  1:21 ` [PATCH 5/6] phylib: remove unused adjust_state callback Sergei Shtylyov
2014-01-04  1:23 ` [PATCH 6/6] phylib: make phy_scan_fixups() static Sergei Shtylyov
2014-01-05  0:07   ` Sergei Shtylyov
2014-01-04  1:28 ` [PATCH 0/6] phylib: cleanups Sergei Shtylyov
2014-01-04 15:53 ` Richard Cochran
2014-01-04 17:14   ` Sergei Shtylyov
2014-01-04 18:53     ` Sergei Shtylyov
2014-01-05  8:31       ` Richard Cochran
2014-01-05 13:40         ` Sergei Shtylyov
2014-01-06  8:35           ` Richard Cochran
2014-01-04 16:41 ` Sergei Shtylyov

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=52C835B3.80103@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@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).