Re: [PATCH]change 'struct device' -> platform_data to firmware_data

[Greg KH]

On Tue, Jan 11, 2005 at 07:54:46PM -0800, Deepak Saxena wrote:
> 
> So the question I have is whether we are using the field as intended
> or we have overloaded it with our own purposes?

You have used it for your own purposes :)

But I would argue that you used it in a way that works, and solves a
real need.  As the intent of this field was never really properly
conveyed, and since you were here first, hey, your implementation gets
to stay!

> If we are doing things incorrectly, I am not argueing that our usage
> has to the way it sits. We could create a new generic serial_device and 
> flash_device structures and subsystems for these, but that requires 
> rewriting drivers and board ports; however, we need enough time
> to work with appropriate subsystem maintainers to do so. My suggestion
> is to add a new firmware_data field for use by ACPI ATM while we
> clean things up in ARM world if so required.  Since ACPI is non-existent 
> on ARM systems, another option is that we keep using the renamed data
> structure as we have been doing. /me votes for this option

I like the "just add a firmware_data" field option too.  It doesn't
break any existing code, and the term "firmware" tells driver authors to
back away from it and not touch it (and we need to add the proper
documentation saying this.)

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/