From: Christoph Hellwig <hch@infradead.org>
To: Ray Bryant <raybry@sgi.com>
Cc: Ray Bryant <raybry@austin.rr.com>, Andrew Morton <akpm@osdl.org>,
lse-tech@lists.sourceforge.net,
"Martin J. Bligh" <mbligh@aracnet.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] lockmeter: fixes
Date: Fri, 17 Sep 2004 20:31:58 +0100 [thread overview]
Message-ID: <20040917203158.A16855@infradead.org> (raw)
In-Reply-To: <414B3270.2080409@sgi.com>; from raybry@sgi.com on Fri, Sep 17, 2004 at 01:52:32PM -0500
> Yes, I'll take a look at it as soon as I get done chasing the COOL bits changes.
>
> Is there a specific example you can point me at as to how others have done this?
Just grep for create_proc_entry - lots of drivers are using this. In fact I wonder
whether a miscdevice wouldn't be the better choice for lockmeter, but given that'd
need userland changes let's stay away from that for now.
next prev parent reply other threads:[~2004-09-17 19:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 23:03 [PATCH 0/3] lockmeter: fixes Ray Bryant
2004-09-16 23:03 ` [PATCH 1/3] lockmeter: fixed-up: lockmeter fixes for preempt case Ray Bryant
2004-09-16 23:04 ` [PATCH 2/3] lockmeter: lockmeter fix for generic_read_trylock Ray Bryant
2004-09-16 19:20 ` Zwane Mwaikambo
2004-09-16 23:38 ` Ray Bryant
2004-09-16 23:04 ` [PATCH 3/3] lockmeter: lockmeter fix for inline in_lock_functions() Ray Bryant
2004-09-17 7:31 ` [PATCH 0/3] lockmeter: fixes Christoph Hellwig
2004-09-17 18:52 ` Ray Bryant
2004-09-17 19:31 ` Christoph Hellwig [this message]
2004-09-19 11:15 ` Alexander Nyberg
2004-09-19 22:39 ` Ray Bryant
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=20040917203158.A16855@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mbligh@aracnet.com \
--cc=raybry@austin.rr.com \
--cc=raybry@sgi.com \
--cc=zwane@linuxpower.ca \
/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