From: Randy Dunlap <randy.dunlap@oracle.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
Deepak Saxena <dsaxena@plexity.net>
Subject: Re: [PATCH] Add device addition/removal notifier
Date: Thu, 19 Oct 2006 08:55:28 -0700 [thread overview]
Message-ID: <20061019085528.45a5771e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1161244591.10524.45.camel@localhost.localdomain>
On Thu, 19 Oct 2006 17:56:31 +1000 Benjamin Herrenschmidt wrote:
> Index: linux-cell/include/linux/device.h
> ===================================================================
> --- linux-cell.orig/include/linux/device.h 2006-10-19 17:43:58.000000000 +1000
> +++ linux-cell/include/linux/device.h 2006-10-19 17:44:24.000000000 +1000
> @@ -427,6 +427,22 @@ extern int (*platform_notify)(struct dev
>
> extern int (*platform_notify_remove)(struct device * dev);
>
> +/**
> + * Device notifiers. Get notified of addition/removal of devices
> + * and possibly other events in the future. Replacement for the
> + * platform "fixup" functions. This is a low level hook provided
> + * for the platform to initialize private parts of struct device,
> + * like firmware related links. Add is called before the device is
> + * added to a bus (and thus the driver probed) and Remove is called
> + * afterward.
> + */
That's not kernel-doc, so please don't begin it with "/**".
---
~Randy
next prev parent reply other threads:[~2006-10-19 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 7:56 [PATCH] Add device addition/removal notifier Benjamin Herrenschmidt
2006-10-19 15:55 ` Randy Dunlap [this message]
2006-10-20 1:53 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 1:55 Benjamin Herrenschmidt
2006-10-20 3:26 ` Greg KH
2006-10-20 4:29 ` Benjamin Herrenschmidt
2006-10-20 4:44 ` Greg KH
2006-10-20 5:42 ` Benjamin Herrenschmidt
2006-10-20 6:16 ` Greg KH
2006-10-20 7:19 ` Benjamin Herrenschmidt
2006-10-20 7:35 ` Benjamin Herrenschmidt
2006-10-20 10:08 ` Paul Mackerras
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=20061019085528.45a5771e.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=dsaxena@plexity.net \
--cc=greg@kroah.com \
--cc=len.brown@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox