linux-kernel - Re: [RFC PATCH 0/2] managed token devres interfaces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Apr 2014 12:04:35 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	shuah.kh@...sung.com
Cc:	Greg KH <gregkh@...uxfoundation.org>, m.chehab@...sung.com,
	tj@...nel.org, rafael.j.wysocki@...el.com, linux@...ck-us.net,
	toshi.kani@...com, linux-kernel@...r.kernel.org,
	linux-media@...r.kernel.org, shuahkhan@...il.com
Subject: Re: [RFC PATCH 0/2] managed token devres interfaces

> >>   - 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/