On Mon, Aug 8, 2016 at 8:46 AM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > On Fri, Jul 22, 2016 at 5:33 PM, Paul Moore <paul@xxxxxxxxxxxxxx> wrote: >> On Thu, Jul 21, 2016 at 7:09 PM, James Morris <jmorris@xxxxxxxxx> wrote: >>> On Thu, 21 Jul 2016, Paul Moore wrote: >>>> James, assuming the overlayfs-next branch is pulled during the merge >>>> window, can you rebase your linux-security#next branch to v4.8-rc1 >>>> once Linus tags it? >>> >>> Yep. >> >> On Fri, Jul 22, 2016 at 3:05 AM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: >>> On Thu, Jul 21, 2016 at 11:16 PM, Paul Moore <paul@xxxxxxxxxxxxxx> wrote: >>>> Hi Vivek, >>>> >>>> These patches look fine to me, thanks for all your hard work and to >>>> everyone who helped review and provide feedback. I have tagged these >>>> patches for merging into the SELinux next branch after this merge >>>> window. >>>> >>>> Miklos, this patchset depends on patches in your overlayfs-next >>>> branch, I assume you're pushing that branch during the upcoming merge >>>> window? >>> >>> Yes, that's the plan. >> >> Great, thanks. > > Base patches are now in v4.8-rc1. Thanks, I've already pinged James to rebase the linux-security tree, once he does I'll merge the SELinux/overlayfs patches into the SELinux next branch. -- paul moore www.paul-moore.com -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
