Le 21/02/2017 à 11:26, Boris Brezillon a écrit :

On Tue, 21 Feb 2017 12:03:45 +0200
Andy Shevchenko [off-list ref] wrote:

quoted

On Tue, Feb 21, 2017 at 10:06 AM, Boris Brezillon
[off-list ref] wrote:

quoted

On Tue, 21 Feb 2017 01:54:37 +0200
Andy Shevchenko [off-list ref] wrote:
 

quoted

On Tue, Feb 21, 2017 at 1:40 AM, Andy Shevchenko
[off-list ref] wrote:  

quoted

On Mon, Feb 20, 2017 at 10:50 PM, Boris Brezillon
[off-list ref] wrote:  

quoted

On Mon, 20 Feb 2017 21:38:03 +0100
Boris Brezillon [off-list ref] wrote:
 

quoted

On Mon, 20 Feb 2017 22:27:17 +0200
Andy Shevchenko [off-list ref] wrote:
 

quoted

On Mon, Feb 20, 2017 at 2:28 PM, Boris Brezillon
[off-list ref] wrote:
 

quoted

 drivers/mtd/nand/atmel/nand-controller.c | 2269 +++++++++++++++++++++++++++
 drivers/mtd/nand/atmel_nand.c            | 2479 ------------------------------  

Does -M -C help you?
At least it would help reviewers
 

No it doesn't, because files were not just moved around using git mv,
it's a complete rewrite of the driver. IIUC, you're about to review
this submission, or are you just trolling like last time?  

My bad, I mistaken you with someone else. Sorry for being harsh, but my
explanation stands ;-).  

No problem. I was asking since it so big and on first glance looks
like a partial copy (I dunno if parameter to -C makes it somehow
useful), though I can't review this. It's too big to me. Sorry I'm
really not trolling, just didn't read commit message carefully.  

Okay, I very quickly looked into the code, what I noticed
- you like extra parens and empty lines in some cases (not big deal)  

Can you point specific places where you think these are not needed?  

1. For example,

#define ATMEL_NFC_CMD(pos, cmd)                        ((cmd) <<
(((pos) * 8) + 2))

Well, I like to explicitly put parenthesis even when operator
precedence guarantees the order of the calculation ('*' is preceding
'+').

Yes

For the parenthesis around (cmd) and (pos), they are required to
guarantee that things like ATMEL_NFC_CMD(x + y, cmd) are working
correctly.

Absolutely.


Even when it's not needed, please keep this habit of using more
parenthesis than required by precedence to make code clearer.

quoted

 *events ^= (status & *events);

I agree with this one, it's uneeded.

quoted

 (((x) * 0x4) + 0x28)

See my comment about ATMEL_NFC_CMD().

quoted

  memset(&si[1], 0, sizeof(s16) * ((2 * strength) - 1));

Ditto.

quoted

Perhaps more in the code. I'm not a LISP programmer.

[..]

quoted

8. Have you checked what kernel library provides?

I think so, but again, this is really vague, what kind of
open-coded functions do you think could be replaced with core libraries
helpers?

quoted

And I believe there are still issues like those. After, who is on
topic, might even find some logical and other issues...

P.S. TBH, so big change is unreviewable in meaningful time. To have a
comprehensive review I, for example, spend ~1h/250LOC, and
~2.5h/1000LOC, I would estimate ~4h/2000LOC. Imagine one to spend one
day for this. Any volunteer? Not me.

I'm not asking you to review the whole driver, but you started to
comment on the code without pointing clearly to the things you wanted
me to address.

Moreover, it's not like if the driver would come without previous code.
So, this re-factoring comes with the experience of previous driver and
its aim is to be comparable feature-wise with the old one. So the amount
of changes doesn't surprise me.

As Boris noted in his patch series, additional optimization and use of
common BCH code can be studied afterwards.

Best regards,
-- 
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html