From: yani.ioannou@gmail.com (Yani Ioannou)
To: lm-sensors@vger.kernel.org
Subject: [RFC PATCH 2.6.12-rc3] dynamic driver sysfs callbacks and RFC on
Date: Thu, 19 May 2005 06:25:57 +0000 [thread overview]
Message-ID: <2538186705050819106031afa6@mail.gmail.com> (raw)
In-Reply-To: <2538186705042422366584aff4@mail.gmail.com>
Hi Dmitry,
Even for static attributes the void * can be very useful, there are
many cases, maybe even most cases (I'm looking through all the sysfs
attribute code looking to update it to take advantage of this patch
now) where static attributes using the void * are fine and the
attribute is not shared amongst different clients/instances of code.
For example, adm1026 we could use the index for that static attributes
as my previous patch shows and we really need a macro in that case. Or
look at net/core/net-sysfs.c, the macros NETDEVICE_SHOW,
NETDEVICE_ATTR, etc are best replaced by static attributes using a
single callback function and using the void *, for which we really
need a macro to set the void *.
Perhaps declaring seperate macros for this (e.g.
DEVICE_ATTRIBUTE_DATA, such as I defined in the adm1026 example patch)
would be more clear?
Thanks,
Yani
On 5/6/05, Dmitry Torokhov <dtor_core@ameritech.net> wrote:
> Hi Yani,
>
> On Friday 06 May 2005 01:40, Yani Ioannou wrote:
> > We would probably want to define another DEVICE_ATTRIBUTE like macro
> > or add a void * parameter to the DEVICE_ATTRIBUTE macro. Any opinions
> > on which way to go? This might be done for the other *_ATTRIBUTE
> > macros too.
> >
>
> No, I don't think so. Again, macros are normally used to initialize
> statically allocated attributes, exposing void * pointer does not do
> them any good. It can only lead to bugs when driver writer misses the
> fact that pointer is shared between all instances of attribute.
>
> --
> Dmitry
>
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:25 [RFC PATCH 2.6.12-rc3] dynamic driver sysfs callbacks and RFC on Yani Ioannou
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Dmitry Torokhov
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Grant Coady
2005-05-19 6:25 ` Dmitry Torokhov
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Dmitry Torokhov
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Grant Coady
2005-05-19 6:25 ` Grant Coady
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Dmitry Torokhov
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Jean Delvare
2005-05-19 6:25 ` Dmitry Torokhov
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou [this message]
2005-05-19 6:25 ` Greg KH
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-19 6:25 ` [RFC PATCH 2.6.12-rc3] dynamic driver sysfs callbacks and RFC Jean Delvare
2005-05-19 6:25 ` [RFC PATCH 2.6.12-rc3] dynamic driver sysfs callbacks and RFC on Yani Ioannou
2005-05-19 6:25 ` Dmitry Torokhov
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=2538186705050819106031afa6@mail.gmail.com \
--to=yani.ioannou@gmail.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.