From: greg@kroah.com (Greg KH)
To: Yani Ioannou <yani.ioannou@gmail.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
Jean Delvare <khali@linux-fr.org>,
LM Sensors <sensors@stimpy.netroedge.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.12-rc4 1/3] dynamic sysfs callbacks
Date: Thu, 19 May 2005 06:25:57 +0000 [thread overview]
Message-ID: <20050511023232.GA7273@kroah.com> (raw)
In-Reply-To: <253818670505101759f4db08d@mail.gmail.com>
On Tue, May 10, 2005 at 08:59:32PM -0400, Yani Ioannou wrote:
> On further reflection, how about I work off this patch for now and for
> each of the derived attributes submit a separate patch implementing
> the callbacks, etc for that attribute along with an example patch
> showing how it can be used to benefit some existing code (these
> already exist for device and class attributes, so I'll resubmit those
> examples).
>
> This way we can be sure that we aren't changing any of the derived
> attributes needlessly, and it presents a better view of exactly what
> changes I'm making to others I suppose :-).
That sounds great, and is what I was trying to get at.
> We should probably document this change somehow in the sysfs
> documentation at some point too.
Yeah, documentation, what a concept... :)
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Yani Ioannou <yani.ioannou@gmail.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
Jean Delvare <khali@linux-fr.org>,
LM Sensors <sensors@stimpy.netroedge.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.12-rc4 1/3] dynamic sysfs callbacks
Date: Tue, 10 May 2005 19:32:32 -0700 [thread overview]
Message-ID: <20050511023232.GA7273@kroah.com> (raw)
In-Reply-To: <253818670505101759f4db08d@mail.gmail.com>
On Tue, May 10, 2005 at 08:59:32PM -0400, Yani Ioannou wrote:
> On further reflection, how about I work off this patch for now and for
> each of the derived attributes submit a separate patch implementing
> the callbacks, etc for that attribute along with an example patch
> showing how it can be used to benefit some existing code (these
> already exist for device and class attributes, so I'll resubmit those
> examples).
>
> This way we can be sure that we aren't changing any of the derived
> attributes needlessly, and it presents a better view of exactly what
> changes I'm making to others I suppose :-).
That sounds great, and is what I was trying to get at.
> We should probably document this change somehow in the sysfs
> documentation at some point too.
Yeah, documentation, what a concept... :)
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 13:21 [PATCH 2.6.12-rc4 1/3] dynamic sysfs callbacks Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-10 22:16 ` Greg KH
2005-05-19 6:25 ` Greg KH
2005-05-11 0:13 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-11 0:59 ` Yani Ioannou
2005-05-19 6:25 ` Yani Ioannou
2005-05-11 2:32 ` Greg KH [this message]
2005-05-19 6:25 ` Greg KH
2005-05-11 6:51 ` Russell King
2005-05-19 6:25 ` Russell King
2005-05-11 7:05 ` Greg KH
2005-05-19 6:25 ` 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=20050511023232.GA7273@kroah.com \
--to=greg@kroah.com \
--cc=dtor_core@ameritech.net \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.com \
--cc=yani.ioannou@gmail.com \
/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.