On Thu, Nov 14, 2013 at 02:35:33AM +, Tony Lindgren wrote:
As we claim to support device tree for mach-omap2, we
should have the necessary flags in the driver to make it
usable.
Cc: Wolfram Sang w...@the-dreams.de
Cc: linux-...@vger.kernel.org
Signed-off-by: Tony Lindgren
* Mark Rutland mark.rutl...@arm.com [131114 03:08]:
Please update Documentation/devicetree/bindings/i2c/i2c-omap.txt
Otherwise, this is fine.
Here's this one with updated documentation.
Regards,
Tony
From: Tony Lindgren t...@atomide.com
Date: Wed, 13 Nov 2013 16:36:37 -0800
Subject:
* Wolfram Sang w...@the-dreams.de [131113 22:59]:
On Wed, Nov 13, 2013 at 06:35:33PM -0800, Tony Lindgren wrote:
As we claim to support device tree for mach-omap2, we
should have the necessary flags in the driver to make it
usable.
Cc: Wolfram Sang w...@the-dreams.de
Cc:
It would have been helpful if the message PATCH [0/x] would have been
sent to the i2c-list also.
Thanks, next time I'll try check the cc list in the cover letter
manually after running git format patch. I guess there's no way
to deal with that in an automated way.
I use this hackish
* Wolfram Sang w...@the-dreams.de [131114 09:49]:
It would have been helpful if the message PATCH [0/x] would have been
sent to the i2c-list also.
Thanks, next time I'll try check the cc list in the cover letter
manually after running git format patch. I guess there's no way
to
On Wed, Nov 13, 2013 at 06:35:33PM -0800, Tony Lindgren wrote:
As we claim to support device tree for mach-omap2, we
should have the necessary flags in the driver to make it
usable.
Cc: Wolfram Sang w...@the-dreams.de
Cc: linux-...@vger.kernel.org
Signed-off-by: Tony Lindgren
