| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20140423151638.GG4781@htj.dyndns.org> Date: Wed, 23 Apr 2014 11:16:38 -0400 From: Tejun Heo <tj@...nel.org> To: Greg KH <gregkh@...uxfoundation.org> Cc: linux-kernel@...r.kernel.org, john@...nmccutchan.com, rlove@...ve.org, eparis@...isplace.org, serge.hallyn@...ntu.com, lennart@...ttering.net, kay@...y.org, lizefan@...wei.com, cgroups@...r.kernel.org, containers@...ts.linux-foundation.org Subject: Re: [PATCHSET cgroup/for-3.16] cgroup: implement cgroup.populated On Tue, Apr 15, 2014 at 12:18:28PM -0400, Tejun Heo wrote: > Hello, Greg. > > On Mon, Apr 14, 2014 at 03:26:58PM -0700, Greg KH wrote: > > Do you want me to pull this branch into my tree for 3.16 now? I have no > > objection to you taking it, if that's easier for you, which ever is fine > > for me. > > I think the best way to proceed would be applying 1-2 to > driver-core-next and then base cgroup/for-3.16 on top of it, but I'd > like to get some feedback from inotify people before proceeding. Greg, can you please apply the first two patches to driver-core-next (or a separate branch which is pulled into driver-core-next, either way works for me as long as the branch is stable)? I'll pull in the branch and route the third patch through cgroup/for-3.16. Thanks! -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists