On Wed, Jun 07, 2017 at 11:16:27PM -0700, Christopher Li wrote: > On Wed, Jun 7, 2017 at 7:47 PM, Luc Van Oostenryck > <luc.vanoostenryck@xxxxxxxxx> wrote: > > The goal of this mini-series is to warn about implicit. > > It's part of a larger series whose goal is to straighten > > situations where the return type of a function doesn't > > match the type of what is returned, often silently and > > with incoherence in the code generated. > > Looks good to me. > > BTW, are those intend to merge into sparse-next or for > review only? It's not something for the release, so for review only. > If it is for sparse-next. I kind of wish to have one dedicate > branch to pull from you. You can still have different branch > for review. It is just went I pull, I don't have to merge between > your branches. Yes, understood. Like for the previous ones, when it will be a pull request it will be clearly so (with 'PULL' in the title and the output of 'git request-pull' in the body). -- Luc -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
