public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Arvid Brodin <arvid.brodin@enea.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Juergen Beisert <jbe@pengutronix.de>
Subject: Re: A standardized way of reporting kernel events to userspace
Date: Sat, 28 May 2011 08:26:32 +0800	[thread overview]
Message-ID: <20110528002632.GA19189@kroah.com> (raw)
In-Reply-To: <4DE02E11.5060007@enea.com>

On Sat, May 28, 2011 at 01:04:49AM +0200, Arvid Brodin wrote:
> Hi,
> 
> After I asked on linux-usb for a way for userspace to catch over-current events
> on the usb bus, it turned out that Juergen Beisert had had the need to do the
> exact same thing some time ago. He posted this patch using a uevent to notify
> userspace:

We've discussed why using uevents for this is not a good idea in the
past, and I don't think anything has changed since then.  You might want
to search the archives for details if you are curious.

As to other solutions, there's always netlink, and people have proposed,
seriously, to put dbus in the kernel to allow it to emit messages that
way.  I don't object to that, and I think there was even some patches
floating around to do that as well.  You might want to revive them and
see if that would fit your requirement here.

hope this helps,

greg k-h

  reply	other threads:[~2011-05-28  0:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 23:04 A standardized way of reporting kernel events to userspace Arvid Brodin
2011-05-28  0:26 ` Greg KH [this message]
2011-05-30  7:56 ` Oliver Neukum

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=20110528002632.GA19189@kroah.com \
    --to=greg@kroah.com \
    --cc=arvid.brodin@enea.com \
    --cc=jbe@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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