On Apr 2, 2013 7:27 PM, "Marek Vasut" <ma...@denx.de> wrote: > > > The only useful thing mxs_spi_setup_transfer() (which > > is no longer called) did in this instance was make that check. > > > > > btw. I was under the impression the MXS SSP block can handle other > > > word-widths than 8 bit, no ? > > > > In theory it can, > > In practice too ;-) > > > however the driver only supports 8-bits and will > > reject anything else. > > Then please at least add a comment about this.
What does that have to do with this patch? There was no comment about it before. You're insisting that changes be broken up to the extent that changing one line of code takes multiple patches! Now you want a comment about existing driver behavior added to patch that doesn't change that behavior? Documenting the driver behavior would seem to be a job for the driver maintainer. If doing this is something I need to do, then maybe I should maintain it? ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
