From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_2 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EEAE8C433E0 for ; Thu, 25 Feb 2021 17:00:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A5AE664F19 for ; Thu, 25 Feb 2021 17:00:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234039AbhBYQ7r (ORCPT ); Thu, 25 Feb 2021 11:59:47 -0500 Received: from mail.kernel.org ([198.145.29.99]:35573 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233906AbhBYQ7D (ORCPT ); Thu, 25 Feb 2021 11:59:03 -0500 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B1BF464E83; Thu, 25 Feb 2021 16:58:21 +0000 (UTC) Date: Thu, 25 Feb 2021 11:58:20 -0500 From: Steven Rostedt To: Viktor Rosendahl Cc: Subject: Re: [PATCH 0/1] Fix for the latency-collector Message-ID: <20210225115820.7a0ec44d@gandalf.local.home> In-Reply-To: <20210225165248.22050-1-Viktor.Rosendahl@bmw.de> References: <20210225165248.22050-1-Viktor.Rosendahl@bmw.de> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 25 Feb 2021 17:52:47 +0100 Viktor Rosendahl wrote: > Hi Steve, > > I am not sure what is the correct approach to handle this latency-collector > fix. Can you take it into your queue? Yes I can take it. I was going to just pull this in for the next merge window as it's not as critical. But because the change is not likely to cause any issues with other parts of the kernel, I'll queue it up for my next push to Linus (as I have some other fixes to send him). -- Steve > > best regards, > > Viktor > > Colin Ian King (1): > tracing/tools: fix a couple of spelling mistakes > > tools/tracing/latency/latency-collector.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) >