From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: shuah.kh@samsung.com
Cc: Greg KH <gregkh@linuxfoundation.org>,
m.chehab@samsung.com, tj@kernel.org, rafael.j.wysocki@intel.com,
linux@roeck-us.net, toshi.kani@hp.com,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
shuahkhan@gmail.com
Subject: Re: [RFC PATCH 0/2] managed token devres interfaces
Date: Thu, 10 Apr 2014 12:04:35 +0100 [thread overview]
Message-ID: <20140410120435.4c439a8b@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <5345CD32.8010305@samsung.com>
> >> - Construct string with (dev is struct em28xx *dev)
> >> format: "tuner:%s-%s-%d"
> >> with the following:
> >> dev_name(&dev->udev->dev)
> >> dev->udev->bus->bus_name
> >> dev->tuner_addr
What guarantees this won't get confused by hot plugging and re-use of the
bus slot ?
I'm also not sure I understand why you can't have a shared parent device
and simply attach the resources to that. This sounds like a problem mfd
already solved ?
Alan
next prev parent reply other threads:[~2014-04-10 11:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 15:21 Shuah Khan
2014-04-09 15:21 ` [RFC PATCH 1/2] drivers/base: add new devres_update() interface to devres_* Shuah Khan
2014-04-09 15:21 ` [RFC PATCH 2/2] drivers/base: add managed token devres interfaces Shuah Khan
2014-04-16 21:58 ` Tejun Heo
2014-04-17 20:01 ` Shuah Khan
2014-04-17 20:10 ` Tejun Heo
2014-04-17 20:22 ` Tejun Heo
2014-04-17 23:27 ` Shuah Khan
2014-04-17 20:50 ` Shuah Khan
2014-04-09 19:17 ` [RFC PATCH 0/2] " Greg KH
2014-04-09 22:44 ` Shuah Khan
2014-04-10 11:04 ` One Thousand Gnomes [this message]
2014-04-10 11:38 ` Mauro Carvalho Chehab
2014-04-10 11:46 ` One Thousand Gnomes
2014-04-10 14:39 ` Mauro Carvalho Chehab
2014-04-11 20:28 ` Shuah Khan
2014-04-14 22:48 ` Shuah Khan
2014-04-10 14:32 ` Shuah Khan
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=20140410120435.4c439a8b@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=m.chehab@samsung.com \
--cc=rafael.j.wysocki@intel.com \
--cc=shuah.kh@samsung.com \
--cc=shuahkhan@gmail.com \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.com \
/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
all inboxes | Powered by JetHome®