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
| ||
|
Date: Thu, 2 May 2013 17:12:06 -0700 From: Tejun Heo <tj@...nel.org> To: Steven Rostedt <rostedt@...dmis.org> Cc: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>, Peter Zijlstra <peterz@...radead.org>, Jens Axboe <axboe@...nel.dk>, Ingo Molnar <mingo@...e.hu>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [patch 4/4] sched: Distangle worker accounting from rq->lock On Tue, Apr 30, 2013 at 06:47:10PM -0400, Steven Rostedt wrote: > On Tue, Apr 30, 2013 at 09:37:22AM -0400, Steven Rostedt wrote: > > [ Blast from the past! ] > > > > When merging in 3.4.42 into the 3.4-rt branch I hit a conflict with the > > try_to_wake_up_local() call. It seems that the 3.4-rt patch has this > > patch applied. Although, this is not applied to any of the other -rt patches. > > > > I take that back. It's in 3.0-rt, 3.2-rt and 3.4-rt, but it's not in 3.6-rt > nor in 3.8-rt. So, it's all good? Or is there something I need to look into? 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