On Wed, Nov 09, 2016 at 02:45:30PM +0530, Kashyap Desai wrote: > > >> please let > > > >> ><stable@xxxxxxxxxxxxxxx> know about it. > > > >> > > > >> There will be follow up patch which I will be sending in sometime > > > >> so follow patch needs to be applied along with this patch. > > > > > > > >Does that mean that this patch on its own is broken? > > > > > > > >confused, > > > Yes this patch is broken and follow up patch will fix that. I am doing > > > some testing with fix and will send it in sometime. > > > > So should I drop this one from the stable trees until that one is > merged? > > Greg - We are sending another patch which is small fix on top of this one. > It is critical regression. > Not sure which will be a good .. To reject or hold current patch. Current > patch is definitely a not good to keep without upcoming fix. > > To avoid confusion, let's reject this patch and apply once full fix is > available (by EOD). Ok, I've dropped this from the stable queue, please let me know when the "fix" is in Linus's tree, so I can re-add this patch, and the fix patch (please let me know what the git ids are for both.) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html