On Mon, Jun 13, 2022 at 3:23 PM Jonathan Corbet <corbet@xxxxxxx> wrote: > Paul Moore <paul@xxxxxxxxxxxxxx> writes: > > > I assumed the doc folks would have picked this up but I don't see it > > in the tree so I'm going to pull it into the selinux/next tree right > > now. Thanks again Randy, I'm sorry for the delay. > > Sorry, the "doc folks" have learned that, in general, folks in the > security subsystems prefer to carry their own patches upward, so I > assumed this one was taken care of. If you'd rather I picked up SELinux > documentation patches, I'd be glad to do so. Hi Jon, I don't care much either way, as long as Linus' tree is correct I'm happy. In this particular case there were no changes under security/selinux so I assumed that the "doc folks" would merge it; I have similar assumptions regarding other subsystems when it comes to SELinux adjacent patches. However, we all know the old joke about making assumptions, so I generally keep tracking those patches for a while and apply them myself if the other subsystems do not. Generally speaking, if I add an Acked-by for a patch I'm not expecting to merge that patch (hence the ACK to let the other maintainer know I'm okay with the patch). Otherwise I'll merge the patch and send a reply to the thread that it has been merged into the relevant SELinux branch. -- paul-moore.com
