From: Pavan Kondeti <pkondeti@codeaurora.org>
To: Greg KH <greg@kroah.com>
Cc: gregkh@suse.de, linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [RFC 1/2] USB: Notify OTG errors to user space via uevents
Date: Tue, 07 Dec 2010 10:30:13 +0530 [thread overview]
Message-ID: <4CFDBF5D.1060806@codeaurora.org> (raw)
In-Reply-To: <20101207044241.GC29392@kroah.com>
On 12/7/2010 10:12 AM, Greg KH wrote:
>>> > > Please don't, this is NOT the way to get errors from the kernel back out
>>> > > to userspace, because, as you have noted, this is not how any other
>>> > > subsystem does it.
>>> > >
>> > Thanks for your feedback. Is there any other way kernel can send errors
>> > to user space asynchronously? is /dev/ interface acceptable?
> Andi Kleen was working on a unified error reporting system for the
> kernel for things like this and other subsystems. Try working with him
> on this as it sounds like it would be what you need.
Thanks for your inputs. I have looked at Andi Kleen's "Unified error
reporting -- A worthy goal?" But it talks mostly about platform errors.
I will work with him and find out if we can use his approach for
notifying OTG errors to user space.
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2010-12-07 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 12:37 [RFC 1/2] USB: Notify OTG errors to user space via uevents Pavankumar Kondeti
2010-12-06 12:37 ` [RFC 2/2] USB: Notify OTG errors from hub driver Pavankumar Kondeti
2010-12-06 15:58 ` [RFC 1/2] USB: Notify OTG errors to user space via uevents Greg KH
2010-12-07 2:32 ` pkondeti
2010-12-07 3:48 ` Pavan Kondeti
2010-12-07 4:22 ` Greg KH
2010-12-07 3:50 ` Greg KH
2010-12-07 4:20 ` Pavan Kondeti
2010-12-07 4:42 ` Greg KH
2010-12-07 5:00 ` Pavan Kondeti [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=4CFDBF5D.1060806@codeaurora.org \
--to=pkondeti@codeaurora.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-arm-msm@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 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.