From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, arjan@linux.intel.com, greg@kroah.com
Subject: Re: [patch] add new uevent
Date: Mon, 08 May 2006 10:24:49 -0700 [thread overview]
Message-ID: <1147109089.3094.1.camel@whizzy> (raw)
In-Reply-To: <20060505222234.GA7238@mipter.zuzino.mipt.ru>
On Sat, 2006-05-06 at 02:22 +0400, Alexey Dobriyan wrote:
> On Fri, May 05, 2006 at 03:13:36PM -0700, Kristen Accardi wrote:
> > Add dock uevents so that userspace can be notified of dock and undock
> > events.
>
> > --- 2.6-git-kca2.orig/include/linux/kobject.h
> > +++ 2.6-git-kca2/include/linux/kobject.h
> > @@ -46,6 +46,8 @@ enum kobject_action {
> > KOBJ_UMOUNT = (__force kobject_action_t) 0x05, /* umount event for block devices (broken) */
> > KOBJ_OFFLINE = (__force kobject_action_t) 0x06, /* device offline */
> > KOBJ_ONLINE = (__force kobject_action_t) 0x07, /* device online */
> > + KOBJ_UNDOCK = (__force kobject_action_t) 0x08, /* undocking */
> > + KOBJ_DOCK = (__force kobject_action_t) 0x09, /* dock */
> > };
> >
> > struct kobject {
> > --- 2.6-git-kca2.orig/lib/kobject_uevent.c
> > +++ 2.6-git-kca2/lib/kobject_uevent.c
> > @@ -48,6 +48,10 @@ static char *action_to_string(enum kobje
> > return "offline";
> > case KOBJ_ONLINE:
> > return "online";
> > + case KOBJ_DOCK:
> > + return "dock";
> > + case KOBJ_UNDOCK:
> > + return "undock";
> > default:
> > return NULL;
> > }
>
> Where exactly are you going to generate them?
Hi Alexey,
These events will be generated from the dock driver. The patch for this
will be submitted in the next day or 2 (assuming everyone is ok with
adding these events).
Kristen
next prev parent reply other threads:[~2006-05-08 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 22:13 [patch] add new uevent Kristen Accardi
2006-05-05 22:22 ` Alexey Dobriyan
2006-05-08 17:24 ` Kristen Accardi [this message]
2006-05-08 18:01 ` Alexey Dobriyan
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=1147109089.3094.1.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=adobriyan@gmail.com \
--cc=arjan@linux.intel.com \
--cc=greg@kroah.com \
--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 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.