public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 09:24:14 -0800	[thread overview]
Message-ID: <20110119172414.GA18010@kroah.com> (raw)
In-Reply-To: <4D371B28.8020501@ixiacom.com>

On Wed, Jan 19, 2011 at 09:11:04AM -0800, Earl Chew wrote:
> Greg,
> 
> I wrote:
> > I think you're telling me you won't accept either of:
> > 
> > a. uio_device_name()
> > b. uio_device_chrdev()
> [ snip ]
> > With no sysfs, I cannot think of a way to get hold of the minor number allocated
> > to this instance of the Linux UIO device, and without that I can't open() the
> > device driver.
> 
> Would you consider :
> 
> 	extern int uio_device_minor(struct uio_info *info);
> 
> ?
> 
> That would allow me to reconstitute the coordinates of the Linux UIO device
> instance from a combination of /proc/devices and a uio_device_minor() query.

Again, no, this is already present in userspace, and no kernel code
should ever need it.

sorry.

greg k-h

  reply	other threads:[~2011-01-19 17:26 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 [this message]
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

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=20110119172414.GA18010@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