From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753803AbaCaShK (ORCPT ); Mon, 31 Mar 2014 14:37:10 -0400 Received: from mail-ve0-f169.google.com ([209.85.128.169]:35586 "EHLO mail-ve0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753154AbaCaShI (ORCPT ); Mon, 31 Mar 2014 14:37:08 -0400 MIME-Version: 1.0 In-Reply-To: <1396290426.5261.80.camel@marge.simpson.net> References: <1396164244.28950.15.camel@marge.simpson.net> <1396239636.5361.57.camel@marge.simpson.net> <1396290426.5261.80.camel@marge.simpson.net> Date: Mon, 31 Mar 2014 11:37:07 -0700 X-Google-Sender-Auth: Bh9ZkLWfuzyklT6pvwwfAmpX3ZA Message-ID: Subject: Re: [PATCH] sched: update_rq_clock() must skip ONE update From: Linus Torvalds To: Mike Galbraith Cc: Peter Zijlstra , Ingo Molnar , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 31, 2014 at 11:27 AM, Mike Galbraith wrote: > > Oh, I didn't cc you because I wanted it applied instantly as ultra > critical, only because the chain of events might be of interest. Ok. That was my main worry, since I was in the process or releasing 3.14, and I just couldn't tell if the patch was something I should worry about or not. And it seems that not applying it was the right thing, which is all that matters by now. Thanks, Linus