From: Greg KH <greg@kroah.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Aritz Bastida <aritzbastida@gmail.com>,
Antonio Vargas <windenntw@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
Date: Wed, 1 Feb 2006 07:11:45 -0800 [thread overview]
Message-ID: <20060201151145.GA3744@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0602011553410.22529@yvahk01.tjqt.qr>
On Wed, Feb 01, 2006 at 03:54:22PM +0100, Jan Engelhardt wrote:
> >>
> >> I guess I could pass three values on the same file, like this:
> >> $ echo "5 1000 500" > meminfo
> >>
> >> I know that breaks the sysfs golden-rule, but how can I pass those
> >> values _atomically_ then? Having three different files wouldn't be
> >> atomic...
> >
> >That's what configfs was created for. I suggest using that for things
> >like this, as sysfs is not intended for it.
> >
> Can't we just somewhat merge all the duplicated functionality between procfs,
> sysfs and configfs...
What "duplicated functionality"? They all do different, unique things.
Patches are always welcome...
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-01 15:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 20:06 Right way to configure a driver? (sysfs, ioctl, proc, configfs,....) Aritz Bastida
2006-01-27 5:01 ` Greg KH
2006-01-27 10:30 ` Aritz Bastida
[not found] ` <69304d110601270834q5fa8a078m63a7168aa7e288d1@mail.gmail.com>
2006-01-30 11:23 ` Aritz Bastida
2006-01-30 21:39 ` Greg KH
2006-02-01 14:54 ` Jan Engelhardt
2006-02-01 15:11 ` Greg KH [this message]
2006-02-01 15:44 ` Aritz Bastida
2006-02-01 16:17 ` Jan Engelhardt
2006-02-02 6:31 ` Neil Brown
2006-01-30 21:41 ` Greg KH
2006-02-01 13:37 ` Aritz Bastida
2006-02-01 13:53 ` linux-os (Dick Johnson)
2006-02-01 14:19 ` Aritz Bastida
2006-02-01 15:11 ` linux-os (Dick Johnson)
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=20060201151145.GA3744@kroah.com \
--to=greg@kroah.com \
--cc=aritzbastida@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=windenntw@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.