On 9 March 2018 at 01:58, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Tue, Mar 6, 2018 at 5:25 AM, Dibyendu Majumdar > <mobile@xxxxxxxxxxxxxxx> wrote: >> >> Chris, I would like to ask for a previous patch to be reverted before >> this goes into actual release. The patch in question introduced the >> invalid PSEUDO_VAL of 0 with size > 64bits. The patch in question is >> this: >> >> https://marc.info/?l=linux-sparse&m=149168635810900&w=2 >> >> I believe this patch is incorrect and moreover is not used by anything >> hence safe to remove. > > Let's deal with it after the 0.5.2 release, together with resubmit of > the pseudo size patch. > Okay. I would like to suggest again to reintroduce sparse-next as the unstable branch for enhancements, while keeping master for bug fixes. I originally wanted stuff to be in master, but that model requires bug fixes on release branch which is not how it happens here. Regards Dibyendu -- 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
