All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [RFC-patch] pc87360 - unchecked
Date: Thu, 17 Aug 2006 20:01:09 +0000	[thread overview]
Message-ID: <20060817200109.GA32692@kroah.com> (raw)
In-Reply-To: <44D2514B.2090202@gmail.com>

On Thu, Aug 17, 2006 at 01:35:30PM -0600, Jim Cromie wrote:
> 
> Jean Delvare wrote:
> >Hi Jim,
> >
> >  
> hi !
> 
> BTW - are you considering these as 18 bugfix material, or are they
> "long standing sub-optimalities" for 19 when it opens ?  (ie when 18 is out)
> 
> Obviously (from the experimentalism in my patches), Ive been treating it 
> as 19 stuff ;-)
> Apologies for making this more *in-need-of-feedback* than it has to be,
> but I guess I cant quite resist..
> 
> >
> >Now I agree that, even then, we probably will never see two 
> of the same kind of  (not that the distinction matters here..)
> >Super-I/O
> >chip on the same board, so that's not really an issue.
> >
> >  
> 
> Um.. I just looked at asb100.c, and Im seeing static decls like:
>        static DEVICE_ATTR(..)
> 
> Unless Im misunderstanding something, this is sufficient to preclude 
> supporting a 2nd device.
> IOW, to support multiple devices, drivers would need to create 
> attributes, groups, etc out of
> kalloc'd memory, sacrificing the (heavy) use of static initialization in 
> hwmon/*.c

No, you are incorrect, it will work just fine.  The dynamic thing is the
struct device, not the functions that make up the file callbacks.

thanks,

greg k-h


  parent reply	other threads:[~2006-08-17 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 19:40 [lm-sensors] [RFC-patch] pc87360 - unchecked Jim Cromie
2006-08-13 19:45 ` Mark M. Hoffman
2006-08-14 13:17 ` Jean Delvare
2006-08-16  5:35 ` Jim Cromie
2006-08-16 21:04 ` Jean Delvare
2006-08-17 19:35 ` Jim Cromie
2006-08-17 20:01 ` Greg KH [this message]
2006-08-17 21:45 ` Jim Cromie
2006-08-18  2:45 ` Mark M. Hoffman
2006-08-18  4:35 ` Greg KH
2006-08-18 11:48 ` Jean Delvare
2006-08-18 21:21 ` Greg KH

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=20060817200109.GA32692@kroah.com \
    --to=greg@kroah.com \
    --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.