On Tue, Jul 23, 2013 at 06:44:56PM +0100, Mark Brown wrote: > On Tue, Jul 23, 2013 at 10:37:11AM -0700, Greg KH wrote: > > On Tue, Jul 23, 2013 at 06:50:29PM +0200, Tomasz Figa wrote: > > > > I fully agree that a simple, single string will not scale even in some, not > > > so uncommon cases, but there is already a lot of existing lookup solutions > > > over the kernel and so there is no point in introducing another one. > > > I'm trying to get _rid_ of lookup "solutions" and just use a real > > pointer, as you should. I'll go tackle those other ones after this one > > is taken care of, to show how the others should be handled as well. > > What are the problems you are seeing with doing things with lookups? You don't "know" the id of the device you are looking up, due to multiple devices being in the system (dynamic ids, look back earlier in this thread for details about that.) > Having to write platform data for everything gets old fast and the code > duplication is pretty tedious... Adding a single pointer is "tedious"? Where is the "name" that you are going to lookup going to come from? That code doesn't write itself... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |