From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Michal Simek <michal.simek@xilinx.com>,
Moritz Fischer <moritz.fischer@ettus.com>
Cc: <joe@perches.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<moritz.fischer.private@gmail.com>
Subject: Re: [PATCH 2/5] net: macb: Fix coding style warnings
Date: Wed, 16 Mar 2016 14:46:03 +0100 [thread overview]
Message-ID: <56E9639B.7020007@atmel.com> (raw)
In-Reply-To: <56E724BB.5030600@xilinx.com>
Le 14/03/2016 21:53, Michal Simek a écrit :
> On 13.3.2016 20:10, 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, as well as a dangling else.
>>
>> Signed-off-by: Moritz Fischer <moritz.fischer@ettus.com>
>> ---
>> drivers/net/ethernet/cadence/macb.c | 101 +++++++++++++++---------------------
>> 1 file changed, 43 insertions(+), 58 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/cadence/macb.c b/drivers/net/ethernet/cadence/macb.c
>> index 4370f37..c2d31c5 100644
>> --- a/drivers/net/ethernet/cadence/macb.c
>> +++ b/drivers/net/ethernet/cadence/macb.c
>> @@ -58,8 +58,7 @@
>>
>> #define GEM_MTU_MIN_SIZE 68
>>
>> -/*
>> - * Graceful stop timeouts in us. We should allow up to
>> +/* Graceful stop timeouts in us. We should allow up to
>> * 1 frame time (10 Mbits/s, full-duplex, ignoring collisions)
>> */
>> #define MACB_HALT_TIMEOUT 1230
>> @@ -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
>
> TBH: I would rather see this converting to kernel-doc format instead of
> using this networking block.
As there is hardly any kernel-doc comments in this driver, I won't force
Moritz to move this one to it.
I would advice, if someone want to move to kernel-doc for some function
comments, to do it in a separate patch (series).
> Also splitting this to more patches will be better. Just by categories
> but that's just my opinion.
Well, yes... but I won't be too picky for such a patch. So here is my:
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Thank for your feedback, bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2016-03-16 13:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 19:10 [PATCH 0/5] net: macb: Checkpatch cleanups Moritz Fischer
2016-03-13 19:10 ` [PATCH 1/5] net: macb: Fix coding style error message Moritz Fischer
2016-03-14 20:47 ` Michal Simek
2016-03-16 13:39 ` Nicolas Ferre
2016-03-13 19:10 ` [PATCH 2/5] net: macb: Fix coding style warnings Moritz Fischer
2016-03-14 20:53 ` Michal Simek
2016-03-16 13:46 ` Nicolas Ferre [this message]
2016-03-13 19:10 ` [PATCH 3/5] net: macb: Address checkpatch 'check' suggestions Moritz Fischer
2016-03-14 20:49 ` Michal Simek
2016-03-16 13:46 ` Nicolas Ferre
2016-03-13 19:10 ` [PATCH 4/5] net: macb: Use ether_addr_copy over memcpy Moritz Fischer
2016-03-14 20:48 ` Michal Simek
2016-03-16 13:48 ` Nicolas Ferre
2016-03-13 19:10 ` [PATCH 5/5] net: macb: Fix simple typo Moritz Fischer
2016-03-14 20:47 ` Michal Simek
2016-03-16 13:51 ` Nicolas Ferre
2016-03-16 13:39 ` [PATCH 0/5] net: macb: Checkpatch cleanups Nicolas Ferre
2016-03-16 16:30 ` Moritz Fischer
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=56E9639B.7020007@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=moritz.fischer.private@gmail.com \
--cc=moritz.fischer@ettus.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).