From: Jonathan Mayer <jonmayer@google.com>
To: dtor_core@ameritech.net
Cc: Patrick Mochel <mochel@digitalimplant.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] added sysdev attribute to sysdev show/store methods - for linux-2.6.13.4
Date: Thu, 20 Oct 2005 15:03:30 -0700 [thread overview]
Message-ID: <4a45da430510201503v74874acoca37bba3aa5a2d07@mail.google.com> (raw)
In-Reply-To: <d120d5000510201459y25a2c8e5v55bf830c445c9dbf@mail.gmail.com>
Surely, the organization of sysfs is logical (by grouping relating
things) rather than functional (by grouping things that need common
back-end interfaces).
Er .. no?
In general, where can I find guidance on where to put things within
sysfs? Has anybody written some kind of Plan?
- jm.
On 10/20/05, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> On 10/20/05, Jonathan Mayer <jonmayer@google.com> wrote:
>
> > 2. it precludes the ability to create sys_device objects whose
> > attributes are not known at compile time (such as an sysfs
> > representation of the smbios table for some platforms -- which will be
> > my next patch submission).
> >
>
> Does this smbios table have to be a system device (does it have to be
> suspended and resumed with interrupts off) or maybe platform bus suits
> it better?
>
> --
> Dmitry
>
next prev parent reply other threads:[~2005-10-20 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 21:47 Jonathan Mayer
2005-10-20 21:59 ` Dmitry Torokhov
2005-10-20 22:03 ` Jonathan Mayer [this message]
2005-10-20 23:03 ` Dmitry Torokhov
2005-10-20 23:07 ` Jonathan Mayer
2005-10-21 0:26 ` Greg KH
2005-10-21 0:42 ` Jonathan Mayer
2005-10-21 4:07 ` Greg KH
2005-10-20 22:00 ` Jonathan Mayer
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=4a45da430510201503v74874acoca37bba3aa5a2d07@mail.google.com \
--to=jonmayer@google.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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®