On Sun, Mar 13, 2016 at 03:08:42PM -0400, Rich Felker wrote: > On Fri, Mar 11, 2016 at 12:06:22PM +0100, David Hildenbrand wrote: > > > > > > > That fixes it for me: > > > > > > > > > > Tested-by: Hans Verkuil <[email protected]> > > > > > > > > > > BTW, your patch is garbled and I had to manually make the change (not > > > > > a big > > > > > deal for a simple change like this). > > > > > > > > > > > > > Thanks for testing. I just copy-pasted the patch, so this was somehow > > > > expected :) > > > > > > > > @maintainers, how to proceed with this? Shall I send that patch again > > > > directly > > > > to the linux-sh list? > > > > > > > > David > > > > > > > How to proceed with this patch? Anyone? > > Sorry for not getting you a response sooner. I don't yet have the > hardware to test this fix on (would like to find some), but it looks > reasonable to me and like it doesn't risk introducing other > regressions. Sato-san, do you have any thoughts or objections to the > patch?
Can you follow up with a well-formed patch that I can apply. No promises since I'm new to kernel maintainership workflow but I'll try to get it in this merge window if I can. Rich
