Dear Mark Brown, > On Fri, Oct 18, 2013 at 04:38:52PM +0200, Marek Vasut wrote: > > I don't quite understand this, is it OK to merge untested patches? I have > > them in my review queue, but I was simply busy so I didn't get to them > > for a while. Fabio is unfortunatelly also N/A now, so things are slow. > > So, I'd prefer not to merge untested stuff but I'm balancing other > considerations here, including getting exposure in -next prior to the > merge window (which is getting close now and the next two weeks are full > of conferences) for a relatively long series. Trent is someone who > generally does good stuff, the code all makes sense and the MXS SPI > driver seems robust so there's nothing setting off alarm bells for me > that this is risky. > > We've still got time to fix or drop the code if there's an issue found > prior to the merge widow opening and even if it makes it into Linus' > tree we can drop anything that causes trouble during the -rcs.
CCing Lothar and Hector, so we have more eyes on this. I got around to test it on M25P80 briefly and so far so good, thanks. Please do test this if possible. Best regards, Marek Vasut ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk _______________________________________________ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
