From: David Brownell <david-b@pacbell.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: Komal Shah <komal_shah802003@yahoo.com>,
akpm@osdl.org, gregkh@suse.de, i2c@lm-sensors.org,
imre.deak@nokia.com, juha.yrjola@solidboot.com,
linux-kernel@vger.kernel.org, r-woodruff2@ti.com,
tony@atomide.com
Subject: Re: [PATCH] OMAP: I2C driver for TI OMAP boards #2
Date: Mon, 31 Jul 2006 16:53:47 -0700 [thread overview]
Message-ID: <200607311653.48240.david-b@pacbell.net> (raw)
In-Reply-To: <20060731181327.d54ce1d0.khali@linux-fr.org>
On Monday 31 July 2006 9:13 am, Jean Delvare wrote:
> If you want things to improve, please help by
> reviewing Komal's driver. I think I understand you already commented on
> it, but I'd like you to really review it, and add a formal approval to
> it (e.g. Signed-off-by or Acked-by). Then I'll review it for merge.
The issues noted in the code are still almost all low priority
(non-blocking).
- The FIXME about choosing the address is very low priority,
and would affect only multi-master systems. The fix would
involve defining a new i2c-specific struct for platform_data,
updating various boards to use it (e.g. OSK can use 400 MHz),
and wouldn't change behavior for any board I've ever seen.
- Likewise with the REVISIT for the bus speed to use. They'd
be fixed with the same patch.
- The REVISIT about maybe a better way to probe is also low
priority; someone with a board that needs better probing
could address it at that time. (Then restest any changes
on multiple generations of silicion ... which IMO is the
role the linux-omap tree should play.)
- The revisit about adap->retries is still up in the air,
and was a question in my submission from last year.
How exactly is that supposed to be used? Right now
it's neither initialized (except to zero) nor tested.
Re coding style issues, I didn't give it a detailed nitpick
but I did easily notice two things worth fixing:
- Some lines are more than 80 characters, so they'll wrap
on standard editor windows.
- There are a couple instances of hidden whitespace to
remove: at end of line, or space-before-tab.
This doesn't include the drivers/Makefile change to push i2c
linkage up near the beginning with other "system" busses,
but that can be a separate patch in any case (assuming that
it's still needed).
Assuming those two coding style things get resolved first,
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
- Dave
next prev parent reply other threads:[~2006-07-31 23:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1154066134.13520.267064606@webmail.messagingengine.com>
2006-07-31 14:33 ` [PATCH] OMAP: I2C driver for TI OMAP boards #2 David Brownell
2006-07-31 16:13 ` Jean Delvare
2006-07-31 16:41 ` David Brownell
2006-07-31 19:10 ` Russell King
2006-07-31 23:55 ` David Brownell
2006-08-01 14:33 ` Tony Lindgren
2006-07-31 19:25 ` Jean Delvare
[not found] ` <200607311713.09820.david-b@pacbell.net>
2006-08-02 7:27 ` Jean Delvare
2006-07-31 23:53 ` David Brownell [this message]
2006-08-02 15:50 ` Jean Delvare
2006-08-02 19:18 ` David Brownell
2006-08-03 9:19 ` Jean Delvare
2006-08-03 14:30 ` David Brownell
2006-08-04 8:31 ` Jean Delvare
[not found] <1153980844.20163.266978546@webmail.messagingengine.com>
2006-08-02 15:34 ` Jean Delvare
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=200607311653.48240.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=i2c@lm-sensors.org \
--cc=imre.deak@nokia.com \
--cc=juha.yrjola@solidboot.com \
--cc=khali@linux-fr.org \
--cc=komal_shah802003@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--cc=tony@atomide.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