All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [RFC-patch 3/3] SuperIO locks coordinator - use in
Date: Sun, 19 Nov 2006 20:46:23 +0000	[thread overview]
Message-ID: <20061119214623.236ceb38.khali@linux-fr.org> (raw)

On Mon, 25 Sep 2006 22:33:49 -0600, David Hubbard wrote:
> Now, I'm not the most knowledgeable one about the I2C subsystem, but I
> believe that w83627ehf_driver is redeclared a little later with this:
> 
> static struct i2c_driver w83627ehf_driver = {
> 	.driver = {
> 		.name	= "w83627ehf",
> 	},
> 	.attach_adapter	= w83627ehf_detect,
> 	.detach_client	= w83627ehf_detach_client,
> };
> 
> 
> Jean mentioned that it might be a good idea to define .name at
> runtime, depending on whether a w83627ehf or a w83627dhg was detected.

No, the name which depends on the device is the (surprise!) device
name, not the driver name. As the w83627ehf driver currently is based
on i2c-isa, this is the name field of an i2c_client structure. The
driver name must match the source file name, so it's not supposed to
change.

-- 
Jean Delvare


             reply	other threads:[~2006-11-19 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 20:46 Jean Delvare [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-06 10:29 [PATCH] watchdog: add support for w83697hg chip Samuel Tardieu
2006-09-09 15:25 ` Alan Cox
2006-09-09 18:02   ` [lm-sensors] " Sergey Vlasov
2006-09-14  7:05     ` [lm-sensors] [RFC-patch 0/3] SuperIO locks coordinator (was: Jim Cromie
2006-09-14  7:20       ` [lm-sensors] [RFC-patch 3/3] SuperIO locks coordinator - use in Jim Cromie
2006-09-26  4:33         ` David Hubbard
2006-09-26 14:12         ` Jim Cromie

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=20061119214623.236ceb38.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.