Re: [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver

[Jean Delvare]

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@xxxxxxxxxx>
> Reviewed-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> Reviewed-by: Alexey Dobriyan <adobriyan@xxxxxxxxx>
> Reviewed-by: Jean Delvare <khali@xxxxxxxxxxxx>
> Cc: David Brownell <david-b@xxxxxxxxxxx>
> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> ---
> 
>  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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/