From: Joe Perches <joe@perches.com>
To: Moritz Fischer <moritz.fischer@ettus.com>, nicolas.ferre@atmel.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] net: macb: Fix more coding style issues
Date: Mon, 07 Mar 2016 09:25:38 -0800 [thread overview]
Message-ID: <1457371538.4085.16.camel@perches.com> (raw)
In-Reply-To: <1457367460-9123-3-git-send-email-moritz.fischer@ettus.com>
On Mon, 2016-03-07 at 08:17 -0800, Moritz Fischer wrote:
> This commit takes care of the coding style warnings
> that are mostly due to a different comment style and
> lines over 80 chars.
[]
> diff --git a/drivers/net/ethernet/cadence/macb.c b/drivers/net/ethernet/cadence/macb.c
[]
> @@ -127,8 +126,7 @@ static void hw_writel(struct macb *bp, int offset, u32 value)
> writel_relaxed(value, bp->regs + offset);
> }
>
> -/*
> - * Find the CPU endianness by using the loopback bit of NCR register. When the
> +/* Find the CPU endianness by using the loopback bit of NCR register. When the
> * CPU is in big endian we need to program swaped mode for management
swaped/swapped typo
@@ -945,6 +943,7 @@ static int macb_rx_frame(struct macb *bp, unsigned int first_frag,
> static int macb_rx(struct macb *bp, int budget)
> {
> int received = 0;
> + int dropped;
This is an unnecessary and unmentioned change.
> unsigned int tail;
> int first_frag = -1;
>
> @@ -968,7 +967,6 @@ static int macb_rx(struct macb *bp, int budget)
> }
>
> if (ctrl & MACB_BIT(RX_EOF)) {
> - int dropped;
> BUG_ON(first_frag == -1);
>
> dropped = macb_rx_frame(bp, first_frag, tail);
>
next prev parent reply other threads:[~2016-03-07 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 16:17 [PATCH 0/3] net: macb: Fix coding style issues Moritz Fischer
2016-03-07 16:17 ` [PATCH 1/3] net: macb: Fix coding style error message Moritz Fischer
2016-03-07 16:17 ` [PATCH 2/3] net: macb: Fix more coding style issues Moritz Fischer
2016-03-07 17:25 ` Joe Perches [this message]
2016-03-07 18:49 ` David Miller
2016-03-07 19:47 ` Moritz Fischer
2016-03-07 16:17 ` [PATCH 3/3] net: macb: Address checkpatch 'check' suggestions Moritz Fischer
2016-03-07 16:17 ` [PATCH 3/3] net: macb: Cleanup checkpatch checks Moritz Fischer
2016-03-07 16:19 ` Moritz Fischer
2016-03-07 17:13 ` [PATCH 0/3] net: macb: Fix coding style issues Nicolas Ferre
2016-03-09 16:29 ` Michal Simek
2016-03-09 17:18 ` Moritz Fischer
2016-03-09 17:22 ` David Miller
2016-03-09 17:29 ` Michal Simek
2016-03-09 20:26 ` David Miller
2016-03-08 7:06 ` Alexander Stein
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=1457371538.4085.16.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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