Thread (22 messages) flat view 22 messages, 4 authors, 2012-07-03
STALE5189d

Revision v1 of 27 in this series.

Revisions (27)
  1. v0 [diff vs current]
  2. v0 [diff vs current]
  3. v0 [diff vs current]
  4. v0 [diff vs current]
  5. v0 [diff vs current]
  6. v1 [diff vs current]
  7. v1 [diff vs current]
  8. v1 [diff vs current]
  9. v1 current
  10. v1 [diff vs current]
  11. v1 [diff vs current]
  12. v1 [diff vs current]
  13. v1 [diff vs current]
  14. v2 [diff vs current]
  15. v2 [diff vs current]
  16. v2 [diff vs current]
  17. v2 [diff vs current]
  18. v3 [diff vs current]
  19. v3 [diff vs current]
  20. v3 [diff vs current]
  21. v3 [diff vs current]
  22. v4 [diff vs current]
  23. v4 [diff vs current]
  24. v5 [diff vs current]
  25. v5 [diff vs current]
  26. v6 [diff vs current]
  27. v7 [diff vs current]

[PATCH 1/3] mfd: support 88pm80x in 80x driver

From: arnd@arndb.de (Arnd Bergmann)
Date: 2012-06-28 14:32:23

On Thursday 28 June 2012, Mark Brown wrote:
Show Details
  On Thu, Jun 28, 2012 at 11:21:56AM +0000, Arnd Bergmann wrote:
quoted
What platform is this driver for?
 - If it's for an existing platform that does not have DT support, please
   include the platform changes for that platform so we can see what gets
   done in there.
This is really not normal practice for device drivers, it'd be a serious
obstacle to getting drivers integrated if we have to have a board merged
with every driver.
But it would be very helpful to see how the platform data is set, especially
with the callback. If the callback is just there to set up a regulator
or clock, then it should be changed to a more generic way.

	Arnd
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help