From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Regarding to CPU hotplug
Date: Mon, 10 Sep 2007 14:08:09 +0000 [thread overview]
Message-ID: <20070910140808.GB6171@kroah.com> (raw)
In-Reply-To: <OF1E936790.FCEE2367-ON65257352.001D2EE5-65257352.001D2710@in.ibm.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
On Mon, Sep 10, 2007 at 01:54:46PM +0530, Omprakash Vishnoi wrote:
> Hi Greg,
>
> I m talking about user space,can u tell me how can i listen dbus
> event,How can i see event coming from HAL
dbus and HAL are userspace things, go see their documentation for how to
do this properly, it is not a kernel issue.
> i don't know,can u tell me please in broad way.No i didn't try to
> those event.I know only about /udev/ directory and how to write rule
> in rule.d directory.
>
> pls tell me what is the approch should i prefer.
Do whatever works properly for you :)
good luck,
greg k-h
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-09-10 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 5:31 Regarding to CPU hotplug Omprakash Vishnoi
2007-09-10 7:13 ` Greg KH
2007-09-10 8:36 ` Omprakash Vishnoi
2007-09-10 14:08 ` Greg KH [this message]
2007-09-10 22:46 ` Kay Sievers
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=20070910140808.GB6171@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).