> Is there a good reason to have a ksmbd-specific list instead of pooling all the smb3 knowledge on a > single list, similar to how nfs development works? There are users who subscribe only to ksmbd-specific list since ksmbd is out of tree. So we specified both lists in MAINTAINERS. I do not object to use single list and kill the specific list after ksmbd is merged into mainline. Add CC: Steve, Ronnie, Aurélien. Any opinions? Thanks!
