From: "Bryan O'Sullivan" <bos@pathscale.com>
To: Greg KH <gregkh@suse.de>
Cc: Roland Dreier <rdreier@cisco.com>,
rolandd@cisco.com, akpm@osdl.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: Revenge of the sysfs maintainer! (was Re: [PATCH 8 of 20] ipath - sysfs support for core driver)
Date: Thu, 09 Mar 2006 20:58:13 -0800 [thread overview]
Message-ID: <1141966693.14517.20.camel@camp4.serpentine.com> (raw)
In-Reply-To: <20060310010050.GA9945@suse.de>
On Thu, 2006-03-09 at 17:00 -0800, Greg KH wrote:
> They are in the latest -mm tree if you wish to use them. Unfortunatly
> it might look like they will not work out, due to the per-cpu relay
> files not working properly with Paul's patches at the moment.
Hmm, OK.
> What's wrong with debugfs?
It's not configured into the kernels of either of the distros I use (Red
Hat or SUSE). I can't have a required part of my driver depend on a
feature that's not enabled in the major distro kernels.
I'd like a mechanism that is (a) always there (b) easy for kernel to use
and (c) easy for userspace to use. A sysfs file satisfies a, b, and c,
but I can't use it; a sysfs bin file satisfies all three (a bit worse on
b), but I can't use it; debugfs isn't there, so I can't use it.
That leaves me with few options, I think. What do you suggest? (Please
don't say netlink.)
<b
next prev parent reply other threads:[~2006-03-10 4:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ef8042c934401522ed3f.1141922821@localhost.localdomain>
2006-03-09 23:18 ` [PATCH 8 of 20] ipath - sysfs support for core driver Roland Dreier
2006-03-09 23:32 ` Bryan O'Sullivan
2006-03-10 0:35 ` Revenge of the sysfs maintainer! (was Re: [PATCH 8 of 20] ipath - sysfs support for core driver) Greg KH
2006-03-10 0:46 ` Bryan O'Sullivan
2006-03-10 1:00 ` Greg KH
2006-03-10 4:58 ` Bryan O'Sullivan [this message]
2006-03-10 6:34 ` Greg KH
2006-03-10 15:53 ` Dave Jones
2006-03-10 7:57 ` Arjan van de Ven
2006-03-10 13:51 ` Bryan O'Sullivan
2006-03-10 14:06 ` Arjan van de Ven
2006-03-10 15:55 ` Bryan O'Sullivan
2006-03-10 16:24 ` Arjan van de Ven
2006-03-10 16:36 ` Bryan O'Sullivan
2006-03-10 16:41 ` Arjan van de Ven
2006-03-10 16:25 ` Dave Jones
2006-03-10 16:35 ` Bryan O'Sullivan
2006-03-10 16:48 ` Greg KH
2006-03-10 16:49 ` Bryan O'Sullivan
2006-03-10 15:55 ` Dave Jones
2006-03-10 13:58 ` [openib-general] " Talpey, Thomas
2006-03-09 23:46 ` [PATCH 8 of 20] ipath - sysfs support for core driver Greg KH
2006-03-09 23:48 ` Roland Dreier
2006-03-09 23:59 ` Bryan O'Sullivan
2006-03-10 1:02 ` 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=1141966693.14517.20.camel@camp4.serpentine.com \
--to=bos@pathscale.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=rolandd@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox