You think a security tree based on 3.13-rc7 is good and Paul, who tested on the actual release of 3.13 is bad? I know you got yelled at for randomly picking fast forward-ish merge points, but now you've got a crappy merge point. Apparently, it was needed it for the Xen/TPM work (not sure why YOU merged it instead of the TPM people, but that's beside the point). But the problem stands. You are based on a crummy location. When are you going to pick up 3.13? After 3.14 is out? Seems like Paul's move to include 3.13 made a lot of sense... On Sun, Mar 16, 2014 at 11:51 PM, James Morris <jmorris@xxxxxxxxx> wrote: > On Fri, 14 Mar 2014, Paul Moore wrote: > >> Hi James, >> >> Here are the SELinux patches for 3.15. There are three patches here, the >> first and last are obvious fixes and the middle patch is a straightforward >> DAC-before-MAC fix. They should merge into the linux-security tree without >> problem. >> >> Enjoy, >> -Paul > > Your tree is ahead of mine wrt Linus. It doesn't apply. > > > > > -- > James Morris > <jmorris@xxxxxxxxx> > -- > To unsubscribe from this list: send the line "unsubscribe linux-security-module" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
