On Sun, Apr 5, 2020 at 6:50 AM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > > > I see that exfat has landed in Linus' tree for 5.7 and is no longer in > > staging. Could backporting exfat from there into Fedora's 5.6 kernel > > tree be done so that we have exfat support in Fedora 32 at GA? > > It landed upstream Friday and won't land into a Fedora kernel build > until Monday, and hence not a rawhide compose until Tuesday and he > which is the same day as we freeze F-32 so I personally don't think > it's worth the risk. Sure it's new functionality but I personally > think we're better off letting it bake in rawhide for a bit and let it > land into F-32 once it's rebased to 5.7 and it's had some time to > prove out a bit. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/staging/exfat/exfat_super.c?h=v5.6.2 I know that there are some significant mm related changes in the 5.7 cycle, because I saw Andrew Morton's heads up email. It also includes vfs changes. I have no idea to what degree exFAT depends on the things being changed, but it may not be simple to just take 5.7's exfat and move it into 5.6. While exfat is self-contained in that exfat changes don't affect anything else in the kernel; the reverse isn't the case. Another way to look at it, if something blows up, how are we going to fix it? What if it blows up only on Fedora and not in mainline 5.7 or 5.6? -- Chris Murphy _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
