From: David Woodhouse <dwmw2@infradead.org>
To: Nicolas Pitre <nico@cam.org>
Cc: mark.langsdorf@amd.com, mtd@infradead.org
Subject: Re: Odd behavior of JFFS with AMD chips - kernel panic!
Date: Tue, 05 Dec 2000 09:03:04 +0000 [thread overview]
Message-ID: <5734.976006984@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012041525460.16670-100000@xanadu.gn.com>
nico@cam.org said:
> David --> This is really really misleading and non-intuitive. Is
> there a good reason to have a separate device node only for read-only
> access?
No good reason. I inherited the device nodes from a previous driver - as
they're already been registered, it made sense at the time to use them as
they were.
I'm reluctant to change them now unless we register a new major number for
them, to prevent confusion. Changing them but keeping the same major# would
even bite the people who _did_ bother to read the documentation and/or run
the provided MAKEDEV script. :)
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next prev parent reply other threads:[~2000-12-05 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-04 18:29 Odd behavior of JFFS with AMD chips - kernel panic! mark.langsdorf
2000-12-04 20:32 ` Nicolas Pitre
2000-12-04 21:49 ` Nicolas Pitre
2000-12-05 9:03 ` David Woodhouse [this message]
2000-12-05 14:43 ` Nicolas Pitre
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=5734.976006984@redhat.com \
--to=dwmw2@infradead.org \
--cc=mark.langsdorf@amd.com \
--cc=mtd@infradead.org \
--cc=nico@cam.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