On Friday 28 September 2012 09:45 PM, Stephen Warren wrote: > > 2) The downstream driver is significaly different from the current > code. I believe a patch to re-add the downstream driver (with > appropriate cleanup) will be much simpler to review if it's a new > file rather than randomly interspered with essentially unrelated > existing code. > > Signed-off-by: Stephen Warren<swar...@nvidia.com> > --- > Mark, > > If this can be taken through the SPI tree for 3.7 that'd be great. If > it needs to be deferred to 3.8, we will need to start talking dependencies, > since I'd like to take a patch through the Tegra tree to delete mach/dma.h > in 3.8. > ---
Acked by: Laxman Dewangan <ldewan...@nvidia.com> It will be great if this goes in k3.7 so that we can post the new driver on K3.8. Definitely it will easy to review along with multiple bug fixes which is done in driver for interfacing different devices like camera/ touch etc. Having all these changes on top of existing one will create more than 10 patches and complicate the review. Also after these many patches, the new driver will be look different than the existing one. ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
