From: Jean Delvare <khali@linux-fr.org>
To: Bryan Wu <bryan.wu@analog.com>
Cc: David Brownell <david-b@pacbell.net>,
Andrew Morton <akpm@linux-foundation.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver
Date: Wed, 21 Mar 2007 18:56:18 +0100 [thread overview]
Message-ID: <20070321185618.96738cbd.khali@linux-fr.org> (raw)
In-Reply-To: <1174471688.5648.56.camel@roc-desktop>
Hi Bryan,
What's the point of setting the Reply-To header to your own address,
other than forcing me to add your name manually each time I reply?
On Wed, 21 Mar 2007 18:08:08 +0800, Wu, Bryan wrote:
> As GPIO based blackfin driver will be replaced by I2C-GPIO generic
> driver, we just update this latest version of blackfin on-chip TWI I2C
> driver according to LKML review.
Good idea.
> [PATCH] Blackfin: on-chip Two Wire Interface I2C driver
>
> The i2c linux driver for blackfin architecture which supports blackfin
> on-chip TWI controller i2c operation.
>
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
> Reviewed-by: Alexey Dobriyan <adobriyan@gmail.com>
> Reviewed-by: Jean Delvare <khali@linux-fr.org>
> Cc: David Brownell <david-b@pacbell.net>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/i2c/busses/Kconfig | 16
> drivers/i2c/busses/Makefile | 1
> drivers/i2c/busses/i2c-bfin-twi.c | 653 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 670 insertions(+)
This is missing a MAINTAINERS entry. Please provide a patch adding it,
and I'm push this patch on my i2c stack (for Linux 2.6.22.)
> +static int __init i2c_bfin_twi_init(void)
> +{
> + int ret;
> +
> + pr_info("I2C: Blackfin I2C TWI driver\n");
> +
> + ret = platform_driver_register(&i2c_bfin_twi_driver);
> + if (ret) {
> + pr_debug("Fail to register i2c_bfin_twi driver\n");
> + }
> + return ret;
> +}
That pr_debug isn't exactly useful. If the registration failed, the
user will notice soon enough, as the driver will not be loaded at all
and modprobe will return the error code (which is more valuable for
debugging than the message itself.)
--
Jean Delvare
next prev parent reply other threads:[~2007-03-21 17:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 10:08 [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver Wu, Bryan
2007-03-21 17:56 ` Jean Delvare [this message]
2007-03-21 18:17 ` Bob Copeland
2007-03-21 19:14 ` Mike Frysinger
2007-03-22 7:03 ` Jean Delvare
2007-03-22 7:13 ` Mike Frysinger
2007-03-21 19:22 ` Jean Delvare
2007-03-22 5:39 ` Mike Frysinger
2007-03-22 7:48 ` Jean Delvare
2007-03-22 8:12 ` Mike Frysinger
2007-03-22 9:24 ` Jean Delvare
2007-03-23 5:46 ` [PATCH -mm try#2] " Wu, Bryan
2007-03-23 7:27 ` Jean Delvare
2007-03-23 7:36 ` Wu, Bryan
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=20070321185618.96738cbd.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@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