From: Paul Mackerras <paulus@samba.org>
To: Greg KH <greg@kroah.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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: Fri, 20 Oct 2006 20:08:27 +1000 [thread overview]
Message-ID: <17720.40987.289776.269230@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20061020061618.GA9432@kroah.com>
Greg KH writes:
> Remember, we didn't add a type identifier to the struct device for a
> reason, comparing the string of the bus type is not a good idea (for
> USB, it will get you in trouble, because two different types of devices
> can be on that bus, who's to say other busses will not also have that
> issue?)
But then we added the dma_map_* API, which only gets the struct device
pointer but needs to do something different depending on what type of
bus the device is on, and possibly even depending on which instance of
its bus type it's on...
If we are going to have APIs like this that work on a struct device,
then we need to have some good way to know what type of bus the device
is on, and what code we need to call to manipulate that bus type.
Paul.
next prev parent reply other threads:[~2006-10-20 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2006-10-23 4:47 ` [PATCH] Call platform_notify_remove later Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-10-19 7:56 [PATCH] Add device addition/removal notifier Benjamin Herrenschmidt
2006-10-19 15:55 ` Randy Dunlap
2006-10-20 1:53 ` Benjamin Herrenschmidt
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=17720.40987.289776.269230@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--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
Powered by JetHome