From: Jean Delvare <khali@linux-fr.org>
To: Bryan Wu <bryan.wu@analog.com>
Cc: i2c@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] Blackfin I2C/TWI driver: add driver descriptions, versions and some module useful information
Date: Sat, 3 Nov 2007 15:14:10 +0100 [thread overview]
Message-ID: <20071103151410.7a7ed29e@hyperion.delvare> (raw)
In-Reply-To: <1193984664-10609-5-git-send-email-bryan.wu@analog.com>
On Fri, 2 Nov 2007 14:24:24 +0800, Bryan Wu wrote:
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> ---
> drivers/i2c/busses/i2c-bfin-twi.c | 19 ++++++++++++-------
> 1 files changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-bfin-twi.c b/drivers/i2c/busses/i2c-bfin-twi.c
> index 727625b..ae41c0b 100644
> --- a/drivers/i2c/busses/i2c-bfin-twi.c
> +++ b/drivers/i2c/busses/i2c-bfin-twi.c
> @@ -37,6 +37,15 @@
> #include <asm/portmux.h>
> #include <asm/irq.h>
>
> +#define DRV_NAME "i2c-bfin-twi"
> +#define DRV_AUTHOR "Sonic Zhang, Bryan Wu"
What's the point this define when you're using it only once, a few
lines below?
> +#define DRV_DESC "Blackfin BF5xx on-chip I2C TWI Contoller Driver"
> +#define DRV_VERSION "1.8"
> +
> +MODULE_AUTHOR(DRV_AUTHOR);
> +MODULE_DESCRIPTION(DRV_DESC);
> +MODULE_LICENSE("GPL");
> +
> #define POLL_TIMEOUT (2 * HZ)
>
> /* SMBus mode*/
> @@ -701,8 +710,8 @@ static int i2c_bfin_twi_probe(struct platform_device *pdev)
> else
> platform_set_drvdata(pdev, iface);
>
> - dev_info(&pdev->dev, "Blackfin I2C TWI controller, regs_base@%p\n",
> - iface->regs_base);
> + dev_info(&pdev->dev, "%s, Version %s, regs_base@%p\n",
> + DRV_DESC, DRV_VERSION, iface->regs_base);
You're mixing device and driver here. DRV_DESC describes the driver,
while this dev_info() refers to a specific device. So I don't see more
confusion than benefit with this change. If you want to expose the
driver version, you'd rather user MODULE_VERSION().
>
> return rc;
>
> @@ -735,7 +744,7 @@ static struct platform_driver i2c_bfin_twi_driver = {
> .suspend = i2c_bfin_twi_suspend,
> .resume = i2c_bfin_twi_resume,
> .driver = {
> - .name = "i2c-bfin-twi",
> + .name = DRV_NAME,
> .owner = THIS_MODULE,
> },
> };
> @@ -750,9 +759,5 @@ static void __exit i2c_bfin_twi_exit(void)
> platform_driver_unregister(&i2c_bfin_twi_driver);
> }
>
> -MODULE_AUTHOR("Sonic Zhang <sonic.zhang@analog.com>");
> -MODULE_DESCRIPTION("I2C-Bus adapter routines for Blackfin TWI");
> -MODULE_LICENSE("GPL");
> -
> module_init(i2c_bfin_twi_init);
> module_exit(i2c_bfin_twi_exit);
--
Jean Delvare
prev parent reply other threads:[~2007-11-03 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 6:24 [PATCH 0/4] Blackfin I2C/TWI driver updates and bug fixing according to Jean's review Bryan Wu
2007-11-02 6:24 ` [PATCH 1/4] Blackfin I2C/TWI driver: Add repeat start feature to avoid break of a bundle of i2c master xfer operation Bryan Wu
2007-11-03 10:46 ` Jean Delvare
2007-11-02 6:24 ` [PATCH 2/4] Blackfin I2C/TWI driver: Add platform_resource interface to support multi-port TWI controllers Bryan Wu
2007-11-03 12:29 ` Jean Delvare
2007-11-02 6:24 ` [PATCH 3/4] Blackfin I2C/TWI driver: add missing pin mux operation Bryan Wu
2007-11-03 13:48 ` Jean Delvare
2007-11-02 6:24 ` [PATCH 4/4] Blackfin I2C/TWI driver: add driver descriptions, versions and some module useful information Bryan Wu
2007-11-03 14:14 ` Jean Delvare [this message]
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=20071103151410.7a7ed29e@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=bryan.wu@analog.com \
--cc=i2c@lm-sensors.org \
--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
all inboxes | Powered by JetHome®