All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Amit Shah <amit.shah@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	virtualization@lists.linux-foundation.org,
	sjur.brandeland@stericsson.com
Subject: Re: [RFC] virtio_console: Add DRIVER and INTERFACE to uevent.
Date: Tue, 22 Jan 2013 08:16:47 -0800	[thread overview]
Message-ID: <20130122161647.GA10600@kroah.com> (raw)
In-Reply-To: <87pq0yw23j.fsf@rustcorp.com.au>

On Tue, Jan 22, 2013 at 09:55:20AM +1030, Rusty Russell wrote:
> sjur.brandeland@stericsson.com writes:
> 
> > From: Sjur Brændeland <sjur.brandeland@stericsson.com>
> >
> > Add information so rproc-serial can be easily recogniced
> > from user space. Add the following information to uevent:
> > DRIVER=virtio_console|virtio_rproc_serial
> > INTERFACE=grand-parent/parent/name
> >
> > Signed-off-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
> > ---
> > Hi,
> >
> > I need some way to identify the major/minor number for
> > the rproc-serial device, given the udev event. 
> > Review comments are welcomed.
> >
> > Thanks,
> > Sjur
> 
> Hmm, I send all uevent questions to Greg KH (CC'd).

The "INTERFACE" uevent variable is only for USB devices, so for anything
else to be sending userspace that variable, would confuse things
greatly.

Sjur, what exactly are you trying to do here?  What do you want
userspace to know, and what should it do with that information?

thanks,

greg k-h

  reply	other threads:[~2013-01-22 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 12:23 [RFC] virtio_console: Add DRIVER and INTERFACE to uevent sjur.brandeland
2013-01-21 23:25 ` Rusty Russell
2013-01-22 16:16   ` Greg KH [this message]
2013-01-24 13:30     ` Sjur Brændeland
2013-01-24 16:51       ` Greg KH
2013-01-25  9:27         ` Amit Shah

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=20130122161647.GA10600@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=amit.shah@redhat.com \
    --cc=mst@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sjur.brandeland@stericsson.com \
    --cc=virtualization@lists.linux-foundation.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 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.