netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dmalcolm@redhat.com
Cc: grundler@parisc-linux.org, netdev@vger.kernel.org
Subject: Re: [PATCH] drivers/net/ethernet/dec/tulip/uli526x.c: fix misleading indentation in uli526x_timer
Date: Wed, 03 Jun 2015 19:44:18 -0700 (PDT)	[thread overview]
Message-ID: <20150603.194418.1009623373928255414.davem@davemloft.net> (raw)
In-Reply-To: <1433273477-52330-1-git-send-email-dmalcolm@redhat.com>

From: David Malcolm <dmalcolm@redhat.com>
Date: Tue,  2 Jun 2015 15:31:17 -0400

> This code in drivers/net/ethernet/dec/tulip/uli526x.c
> function "uli526x_timer":
> 
>   1086          } else
>   1087                  if ((tmp_cr12 & 0x3) && db->link_failed) {
>   [...snip...]
>   1109                  }
>   1110                  else if(!(tmp_cr12 & 0x3) && db->link_failed)
>   1111                  {
>   [...snip...]
>   1117                  }
>   1118                  db->init=0;
> 
> is misleadingly indented: the
>   db->init=0
> is indented as if part of the else clause at line 1086, but it is
> independent of it (no braces before the "if" at line 1087).
> 
> This patch fixes the indentation to reflect the actual meaning of the code,
> though is it actually meant to be part of the "else" clause?  (I'm a
> compiler developer, not a kernel person).  It also adds spaces around
> the assignment, to placate checkpatch.pl.

I think the code is arranged as intended and the indentation is just wrong.

Patch applied, thanks.

      reply	other threads:[~2015-06-04  2:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 19:31 [PATCH] drivers/net/ethernet/dec/tulip/uli526x.c: fix misleading indentation in uli526x_timer David Malcolm
2015-06-04  2:44 ` David Miller [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=20150603.194418.1009623373928255414.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dmalcolm@redhat.com \
    --cc=grundler@parisc-linux.org \
    --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).