From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tim Hockin <thockin@sun.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: /dev/nvram driver
Date: Fri, 22 Jun 2001 15:02:04 -0400 [thread overview]
Message-ID: <3B33962C.7B401F89@mandrakesoft.com> (raw)
In-Reply-To: <3B339380.C0D973CB@sun.com>
Tim Hockin wrote:
> Who is maintaining the /dev/nvram driver? I have a couple things I want to
> suggest/ask.
I haven't seen any patches for ages to nvram, so I presume nobody.
> What I really want to know is: should I bother making nvram_open_cnt SMP
> safe, or should it just go away all together. I vote for the latter
> option, unless something depends on this behavior (in which case, other
> fixes are needed, because it is broken :).
Once you figure out what the best behavior is (which I'm not sure of,
myself), I would suggest using a semaphore in the open and release
methods.
Jeff
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-22 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 18:50 /dev/nvram driver Tim Hockin
2001-06-22 19:02 ` Jeff Garzik [this message]
2001-06-22 22:07 ` Alan Cox
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=3B33962C.7B401F89@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@sun.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.