Received: by 10.223.185.116 with SMTP id b49csp8834042wrg; Fri, 2 Mar 2018 08:43:14 -0800 (PST) X-Google-Smtp-Source: AG47ELu0SxyhszIjS2OXSZjsD/VoUIbP3JUK4Ryjpq8dJKZwrxUhL+dlgVyuYUk6eXLFbZLMsncZ X-Received: by 2002:a17:902:a613:: with SMTP id u19-v6mr5596901plq.92.1520008994251; Fri, 02 Mar 2018 08:43:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520008994; cv=none; d=google.com; s=arc-20160816; b=bP62y95bVRDnuqqfkjrBn3qDAhsyUELm0v683NFlmgIS4HjnCoKM3YBL5kRNJrxvIm Vpk2q8t5ZwRUp/5To0X2ssMI6HfA7WAkyJeX+Q+q8KA9T3+E+/iG0zVNI3vaPFJUX945 LkMw1iA2PbeZmjBla+I4Y2qLIVh9hvZZWhgrF9uyhODz7thlaXPGyaEGqWHojkaVniMd mOJtiLNfh6tU2MY5gSa4WVvSh+6KyW+ybuc9ccPIJir79x7AIxnc+v4xqiv28MBlQ17x YPugf3piofB85AUG5l6ISKyafuIm8i3NmgevjEhgfNbwo7AH2Dj7J60Mf11tXrKv8i7E rd8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=T9m+AhmUYy5T9PzXQ1EotRJ+60rUVUxjfT+7xcKsfjo=; b=hrqKepktGpV1TrarpjXoFmW2vnRNj8b6VCVRJ+Rk6fmIdQ/FEzWj4AJCMrmAeDEWLG YWoA+b+yp7yKy/OcUhQt+1JO3OlpdbQijkYtRJKQjci3uNjcQn40lJrujDD1LxQUwpm+ hRSY8m7e5bF33fcN0cpIwv9sDARAjW4Zj87I8NWvg1gIuv1Z1RgVA+z6pDCOoSfRZdwK cToDMg/GB4yH+LGfPK8vm9+tmIBEOp8EFf2nAcxSu2twcDUDir9cUTqNbzABJAnbxLQk CiEr91lKF/oPHxmLhArE8S9AXjF0vsspNkSIMvs9Rs6r26La06h0OgsV1LSONyKqxJlw NdfA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r65si5154711pfe.295.2018.03.02.08.42.59; Fri, 02 Mar 2018 08:43:14 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034381AbeCBQjG (ORCPT + 99 others); Fri, 2 Mar 2018 11:39:06 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:54544 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034309AbeCBQjD (ORCPT ); Fri, 2 Mar 2018 11:39:03 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1erni1-0001nD-9k; Fri, 02 Mar 2018 17:39:01 +0100 Date: Fri, 2 Mar 2018 17:39:01 +0100 From: Sebastian Andrzej Siewior To: Haris Okanovic Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, tglx@linutronix.de, julia.cartwright@ni.com, gratian.crisan@ni.com, anna-maria@linutronix.de Subject: Re: [PATCH v3 2/2] timers: Don't search for expired timers while TIMER_SOFTIRQ is scheduled Message-ID: <20180302163900.ldnkhgsvqxlki4ju@linutronix.de> References: <20170803210657.19179-1-haris.okanovic@ni.com> <20170803210657.19179-2-haris.okanovic@ni.com> <28f05e39-6bc6-99c5-e1bc-91be3e79ea78@ni.com> <13c06708-f7ad-4f46-1c0b-f12d1ca16beb@ni.com> <20180301164755.pipco45y5nlvmdsy@linutronix.de> <7079102c-f53b-e8ab-c54d-1c40ff21d921@ni.com> <20180302145232.anp4hz25uwqygopa@linutronix.de> <98f4236e-9863-2af7-1170-51cd118f65bd@ni.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <98f4236e-9863-2af7-1170-51cd118f65bd@ni.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-03-02 10:29:56 [-0600], Haris Okanovic wrote: > > Could please point me to the code/patches or something? > > I rebase onto v4.14.20-rt17, running some sanity test before reposting to ml > (cyclictest & Anna's timertest). Will post V4 sometime today (US Central > Time) if everything goes well. > > Are you also asking for a 4.9 version? I'm fine leaving it out of 4.9. Hmmm. Maybe this is a form of miscommunication here :) So my understanding is that you complain/ask why there is an older version of the patch still in v4.9-RT: |It was added back into 4.9 at some point after v4.9.30-rt20. I see an older |version in v4.9.68-rt60, for example, hence my original email. It was dropped |sometime thereafter, presumably because it no longer cleanly applies. I don't |see it in v4.14.20-rt17, for example. So I ask where you see the old version of your patch in v4.9-RT. Yes it was added, then removed and it never appeared back in. However, I don't see anymore in v4.9.68-rt60. > -- Haris Sebastian