On Tue, Jul 04, 2017 at 10:15:23AM +0200, Romain Perier wrote: > Hello, > > > Le 04/07/2017 à 09:41, Greg Kroah-Hartman a écrit : > > On Mon, Jul 03, 2017 at 08:17:38PM +0200, Uwe Kleine-König wrote: > >> Hello Greg, > > Please don't top-post :( > > > >> I'm a bit disappointed that you didn't drop this patch. At the time I > >> sent my review it was still in your tty-testing branch and now it's part > >> of your pull request for 4.13-rc1 (as commit > >> a3015affdf76ef279fbbb3710a220bab7e9ea04b). :-| > > And now it's in Linus's tree! :) > > > >> I'm still convinced that this patch is wrong in its current form. > > Should I revert it, or can I get a fix for it? Reviewing the patch > > when it was submitted would have been best, not after it ends up in one > > of my trees... > > I don't think there is a fix for it. Either you revert the patch and you > code the fix differently, as I suggested by changing dma_rx_callback... > but that's more intrusive... or you keep this patch. I'll revert it after 4.13-rc1 is out, unless there are major objections to that... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
