From: Michal Simek <michal.simek@xilinx.com>
To: David Miller <davem@davemloft.net>, <michal.simek@xilinx.com>
Cc: <nicolas.ferre@atmel.com>, <moritz.fischer@ettus.com>,
<cyrille.pitchen@atmel.com>, <punnaia@xilinx.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] net: macb: Fix coding style issues
Date: Wed, 9 Mar 2016 18:29:01 +0100 [thread overview]
Message-ID: <56E05D5D.80604@xilinx.com> (raw)
In-Reply-To: <20160309.122210.1419008371671612631.davem@davemloft.net>
On 9.3.2016 18:22, David Miller wrote:
> From: Michal Simek <michal.simek@xilinx.com>
> Date: Wed, 9 Mar 2016 17:29:39 +0100
>
>> On 7.3.2016 18:13, Nicolas Ferre wrote:
>>> Le 07/03/2016 17:17, Moritz Fischer a écrit :
>>>> Hi Nicolas,
>>>>
>>>> this series deals with most of the checkpatch warnings
>>>> generated for macb. There are two BUG_ON()'s that I didn't touch, yet,
>>>> that were suggested by checkpatch, that I can address in a follow up
>>>> commit if needed.
>>>> Let me know if you want me to split the fixes differently or squash
>>>> them into one commit.
>>>
>>> Hi,
>>>
>>> I'm not usually fond of this type of patches, but I must admit that this
>>> series corrects some style issues.
>>>
>>> So, I would like more feedback from Michal and Cyrille as these changes
>>> may delay some of the not-merged-yet features or more important
>>> work-in-progress on their side.
>>>
>>> On the other hand, if we all think it's a calm period for this macb
>>> driver, we may find interesting to merge some "cleanup and style"
>>> enhancements.
>>
>> Not a problem with merging cleanups in general. We have several out of
>> tree patches but doesn't make sense to to wait.
>> I wasn't in cc for the series but I don't like this change to be the
>> part of cleanup series.
>>
>> mac = of_get_mac_address(np);
>> if (mac)
>> - memcpy(bp->dev->dev_addr, mac, ETH_ALEN);
>> + ether_addr_copy(bp->dev->dev_addr, mac);
>
> Why? This is what we tell people to use.
I would expect this as separate patch not the part of one huge cleanup
patch which does just comment and space cleanups.
Thanks,
Michal
next prev parent reply other threads:[~2016-03-09 17:29 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
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 [this message]
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=56E05D5D.80604@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=cyrille.pitchen@atmel.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=moritz.fischer@ettus.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=punnaia@xilinx.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;
as well as URLs for NNTP newsgroup(s).