From: Greg KH <greg@kroah.com>
To: Earl Chew <echew@ixiacom.com>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: UIO null parent for __uio_register_device and uio_device_name()
Date: Wed, 19 Jan 2011 14:41:05 -0800 [thread overview]
Message-ID: <20110119224105.GA23401@kroah.com> (raw)
In-Reply-To: <4D376079.8020108@ixiacom.com>
On Wed, Jan 19, 2011 at 02:06:49PM -0800, Earl Chew wrote:
> Hans Koch wrote:
> > There's a small library with helper functions. Among other things, they
> > allow searching the UIO device node by name (the name you gave your device
> > in uio_info->name). The library is here:
> >
> > git://git.linutronix.de/projects/libUIO.git
> >
> > or with gitweb:
> >
> > http://git.linutronix.de/gitweb.cgi?p=projects/libUIO.git;a=summary
>
> Hans, Greg,
>
> I appreciate the chance to discuss this change with you. I do understand your
> point of view, and I can see how libUIO navigates sysfs from userspace
> to figure out what's there.
>
> Unfortunately I am not in a position to mandate the inclusion of sysfs in our
> deployment, and Linux UIO has a dependency on sysfs to be usable.
I still fail to see why sysfs has been deemed "unacceptable".
What is wrong with it that is keeping you from using it? Technical
details please, otherwise there is no way for me to ever be able to fix
them.
thanks,
greg k-h
prev parent reply other threads:[~2011-01-19 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 3:56 RFC: UIO null parent for __uio_register_device and uio_device_name() Earl Chew
2011-01-19 14:56 ` Hans J. Koch
2011-01-19 15:42 ` Earl Chew
2011-01-19 16:30 ` Greg KH
2011-01-19 17:07 ` Earl Chew
2011-01-19 17:11 ` Earl Chew
2011-01-19 17:24 ` Greg KH
2011-01-19 17:22 ` Greg KH
2011-01-19 20:52 ` Hans J. Koch
2011-01-19 22:06 ` Earl Chew
2011-01-19 22:41 ` Greg KH [this message]
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=20110119224105.GA23401@kroah.com \
--to=greg@kroah.com \
--cc=echew@ixiacom.com \
--cc=hjk@hansjkoch.de \
--cc=linux-kernel@vger.kernel.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