From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3 v3] Bit-banged MII driver with multi-bus support.
Date: Thu, 24 Sep 2009 09:35:02 -0400 [thread overview]
Message-ID: <4ABB7586.9040001@ge.com> (raw)
In-Reply-To: <200909241452.05747.luigi.mantellini@idf-hit.com>
Hi Luigi,
Luigi 'Comio' Mantellini wrote:
> (autoreview)
>
> Hi Ben,
>
> I make some changes to the patch, but I will post after your review.
> See my annotation, that will be present into the next patch release.
>
> best regards.
>
> Il mercoled? 23 settembre 2009 15:10:54 Luigi 'Comio' Mantellini ha scritto:
>> From: Luigi 'Comio' Mantellini <luigi.mantellini@idf-hit.com>
>>
>> Signed-off-by: Luigi 'Comio' Mantellini <luigi.mantellini@idf-hit.com>
>> ---
>> drivers/net/phy/miiphybb.c | 324
[snip]
>> +static inline struct bbmiibus *bb_miiphy_getbus(char *devname)
>> +{
>> +#ifdef CONFIG_BITBANGMII_MULTI
>> + /* Search the correct bus */
>> + for (j = 0; j < sizeof(bbmiibusses)/sizeof(bbmmis[0]); j++) {
>
> [COMIO] Changed j to i and add i declaration.
You may have inherited the "j" loop counter from me. I stopped using
"i" in loop counters and started with "j" because most code (variables
and keywords) do not use words with the letter "j" or "k" in them. On
the other hand, A LOT of variables and keywords have "i" in their names.
The result is that it is a PAIN to find loop variable references for
the loop variable "i" but it is usually trivial to find them for "j" and
"k".
Case in point: how many "i"s does your loop have? Just in the for()
loop control line, I count five.
Trivia:
* I find I almost never need to nest loops more than 2 deep, so "j" and
"k" cover almost all loop variable needs.
* I believe Fortran coding conventions started the "ijk" counter mania.
[snip]
> Any comment is welcome
>
> best regards,
>
> luigi
Best regards,
gvb
next prev parent reply other threads:[~2009-09-24 13:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 13:10 [U-Boot] [PATCH 0/3 v3] New MIIPHYBB implementation with multi-bus support Luigi 'Comio' Mantellini
2009-09-23 13:10 ` [U-Boot] [PATCH 1/3 v3] Bit-banged MII driver " Luigi 'Comio' Mantellini
2009-09-23 13:10 ` [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code Luigi 'Comio' Mantellini
2009-09-23 13:10 ` [U-Boot] [PATCH 3/3 v3] Update all board to support new bbmiiphy driver (with multibus support) Luigi 'Comio' Mantellini
2009-10-05 6:34 ` Ben Warren
2009-10-05 6:30 ` [U-Boot] [PATCH 2/3 v3] Add bb_miiphy_init call before any ethernet bring-up code Ben Warren
2009-10-05 20:04 ` Luigi Mantellini
2009-10-05 20:18 ` Ben Warren
2009-10-05 20:35 ` Luigi Mantellini
2009-09-24 12:52 ` [U-Boot] [PATCH 1/3 v3] Bit-banged MII driver with multi-bus support Luigi 'Comio' Mantellini
2009-09-24 13:35 ` Jerry Van Baren [this message]
2009-10-05 6:27 ` Ben Warren
2009-10-05 19:55 ` Luigi Mantellini
2009-10-05 20:04 ` Ben Warren
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=4ABB7586.9040001@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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