From: Martin Schlemmer <azarah@nosferatu.za.org>
To: Tomasz Torcz <zdzichu@irc.pl>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Andreas Jellinghaus <aj@dungeon.inka.de>
Subject: Re: [PATCH] add sysfs mem device support [2/4]
Date: Fri, 26 Dec 2003 22:18:12 +0200 [thread overview]
Message-ID: <1072469891.21020.3.camel@nosferatu.lan> (raw)
In-Reply-To: <20031226165456.GA26466@irc.pl>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
On Fri, 2003-12-26 at 18:54, Tomasz Torcz wrote:
> On Fri, Dec 26, 2003 at 04:19:49PM +0000, Christoph Hellwig wrote:
> > On Thu, Dec 25, 2003 at 09:41:28PM +0200, Martin Schlemmer wrote:
> > > So maybe suggest an solution rather than shooting one down all the
> > > time (which do seem logical, and is only apposed by one person currently
> > > - namely you =).
> >
> > My suggestion is to just use MAKEDEV asis for devices that are static
> > like the memdevices. Dynamic solutions do not buy us anything for those.
>
> They do buy when using tmpfs for /dev.
And it will anyhow require a full evaluation of MAKEDEV (debian's one
anyhow), as it really put a lot of extra crap in. With Greg's patches I
only need to worry about /dev/core, /dev/std{in,out,err} and alsa. The
question is now also how do you 'qualify' an device to have sysfs
support. Sure some is static like /dev/null, but over here /dev/hda is
pretty static as well =)
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-26 20:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:21 [PATCH] some sysfs patches for 2.6.0 [0/4] Greg KH
2003-12-23 0:24 ` [PATCH] fix sysfs oops [1/4] Greg KH
2003-12-23 0:26 ` [PATCH] add sysfs mem device support [2/4] Greg KH
2003-12-23 0:28 ` [PATCH] add sysfs misc device support [3/4] Greg KH
2003-12-23 0:28 ` [PATCH] add sysfs vc device support [4/4] Greg KH
2003-12-23 13:17 ` Christoph Hellwig
2003-12-23 0:29 ` [PATCH] add sysfs misc device support [3/4] Greg KH
2003-12-23 13:16 ` Christoph Hellwig
2003-12-23 13:15 ` [PATCH] add sysfs mem device support [2/4] Christoph Hellwig
2003-12-23 15:31 ` Rob Love
2003-12-23 16:07 ` Rob Love
2003-12-23 16:39 ` Christoph Hellwig
2003-12-23 17:56 ` Rob Love
2003-12-23 20:00 ` Stephan Maciej
2003-12-23 20:33 ` viro
2003-12-25 17:48 ` Andreas Jellinghaus
2003-12-25 18:45 ` Christoph Hellwig
2003-12-25 19:41 ` Martin Schlemmer
2003-12-25 20:57 ` Martin J. Bligh
2003-12-25 22:02 ` Martin Schlemmer
2003-12-26 16:19 ` Christoph Hellwig
2003-12-26 16:54 ` Tomasz Torcz
2003-12-26 20:18 ` Martin Schlemmer [this message]
2003-12-23 18:01 ` Greg KH
2003-12-23 19:16 ` Christoph Hellwig
2003-12-23 19:19 ` Rob Love
2003-12-23 19:22 ` Christoph Hellwig
2003-12-23 19:25 ` Rob Love
2003-12-23 19:42 ` Jeff Garzik
2003-12-23 19:45 ` Rob Love
2003-12-23 19:24 ` viro
2003-12-23 19:28 ` Rob Love
2003-12-23 11:07 ` [PATCH] some sysfs patches for 2.6.0 [0/4] Andreas Jellinghaus
2003-12-23 23:26 ` 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=1072469891.21020.3.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=aj@dungeon.inka.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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