Mark,
could you have another look at these patches maybe? They aren't urgent,
I just want to avoid the get lost.
Thanks for your time,
Daniel
On 25.07.2012 13:44, Daniel Mack wrote:
The spi-gpio driver currently assumes the chipselect gpio number is
stored in -controller_data of the device's
On 01.08.2012 22:51, Mark Brown wrote:
On Wed, Aug 01, 2012 at 10:45:19PM +0200, Daniel Mack wrote:
could you have another look at these patches maybe? They aren't urgent,
I just want to avoid the get lost.
Can you please resend them with me in the CCs? My process for handling
patches is
The spi-gpio driver currently assumes the chipselect gpio number is
stored in -controller_data of the device's static board information.
In devicetree environments, this information is unavailable and has to
be derived from the DT node.
This patch moves the gpio storage to the controller's
On Wed, Jul 25, 2012 at 01:44:11PM +0200, Daniel Mack wrote:
The spi-gpio driver currently assumes the chipselect gpio number is
stored in -controller_data of the device's static board information.
Always CC maintainers on things... you've not CCed Grant or Linus W,
and for now I'm handling
On 25.07.2012 21:52, Mark Brown wrote:
On Wed, Jul 25, 2012 at 09:38:58PM +0200, Daniel Mack wrote:
On 25.07.2012 21:33, Mark Brown wrote:
Always CC maintainers on things... you've not CCed Grant or Linus W,
and for now I'm handling SPI patches (though I'm not in MAINTAINERS so
missing me
On Wed, Jul 25, 2012 at 10:00:18PM +0200, Daniel Mack wrote:
I don't know what's wrong here, but clearly, the message in my inbox has
To: spi-devel-general@lists.sourceforge.net
Cc: grant.lik...@secretlab.ca,
rob.herr...@calxeda.com,
devicetree-disc...@lists.ozlabs.org,
On 25.07.2012 22:12, Mark Brown wrote:
On Wed, Jul 25, 2012 at 10:00:18PM +0200, Daniel Mack wrote:
I don't know what's wrong here, but clearly, the message in my inbox has
To: spi-devel-general@lists.sourceforge.net
Cc: grant.lik...@secretlab.ca,
rob.herr...@calxeda.com,
