Received: by 10.213.65.68 with SMTP id h4csp22306imn; Mon, 26 Mar 2018 14:08:59 -0700 (PDT) X-Google-Smtp-Source: AG47ELv5iD8zb/jCt0FIrNVUtBPkiNTqzA3BH3/Lccr/JqMaLSm6T8GjKw1g45LGqo+m93t3WQFr X-Received: by 2002:a17:902:bb81:: with SMTP id m1-v6mr41274162pls.71.1522098539439; Mon, 26 Mar 2018 14:08:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522098539; cv=none; d=google.com; s=arc-20160816; b=0+UAiJSuhldTS39HqDzf8rl5fdrLkAf05uMI7uRLlXIp6+aPy2o0Sb5U19FmmPV6vF jnDW2SUtZ0dV2XLArdv4rXGBiU3QSVIAn9dm7lZT3Z7HaLQdLdhiwNbQJFuhqqM4NVWZ N6sGIyTkrSPC7mumz3C2ocf+03HJURAF2YGQ81oPpzuQ1UE7t3FBDZ7d/bbHBklp9hcD fOGOQtjAB8RrCghUgfr688lhimpRgVCfKkduQa7LDSWzGbIhk/AKlv7umLizkz8BGkds HfOQMhED5FXlKkW78Myed30hT2RFXPmck1BM/SaJLtqVYoBA+MbtFvdw0OCaToKYmeyE lH3A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dmarc-filter:arc-authentication-results; bh=In0b2pu/Dwbb2FbpDiQRjDk8o+ygbG+RKv0UEmFFUQ4=; b=DF6r+0sdwunq3wJJXjD8HZFthIBWZopfxyGX7L0+eLtTL0RsxrMcKLEYeq7P9WN1Eo Zwq/Vu6DI5UHdyVUShiczLLG0af0K27qu4h9jrLN8jP68m87Ngf+Rkm0+lnl6J0a/+7X x9ilEV/HUnJjLx7b0om8PBGKOM/ujtd9d3RSc6CHe8ML2DWiY03Lx0adsmA1I3ivnQu8 RXnqzPBmW4MGmXAfPXmU1mgeMzAU+sesn5jj0XrqMHqTSjeq40b9uTgBWaBBzWtW4xKR yPQSeow+X8Hia4IzVAJoFO3yfZnAYZjBmtfR4tNTC2JVysQsZFkx8capo56UrblbdQQ6 aOBg== 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 l25si11876841pff.16.2018.03.26.14.08.45; Mon, 26 Mar 2018 14:08:59 -0700 (PDT) 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 S1752180AbeCZVGP (ORCPT + 99 others); Mon, 26 Mar 2018 17:06:15 -0400 Received: from mail.kernel.org ([198.145.29.99]:43866 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752004AbeCZVFc (ORCPT ); Mon, 26 Mar 2018 17:05:32 -0400 Received: from gandalf.local.home (cpe-172-100-180-131.stny.res.rr.com [172.100.180.131]) (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 695DB21773; Mon, 26 Mar 2018 21:05:31 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 695DB21773 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=goodmis.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=rostedt@goodmis.org Date: Mon, 26 Mar 2018 17:05:29 -0400 From: Steven Rostedt To: Alexei Starovoitov Cc: Mathieu Desnoyers , linux-kernel@vger.kernel.org, Alexei Starovoitov , Peter Zijlstra , Ingo Molnar Subject: Re: [RFC PATCH] tracepoint: Provide tracepoint_kernel_find_by_name Message-ID: <20180326170529.214b7e6e@gandalf.local.home> In-Reply-To: <20180326204834.npkr26bdf5aprwnv@ast-mbp.dhcp.thefacebook.com> References: <20180326191031.14939-1-mathieu.desnoyers@efficios.com> <20180326204834.npkr26bdf5aprwnv@ast-mbp.dhcp.thefacebook.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 26 Mar 2018 13:48:36 -0700 Alexei Starovoitov wrote: > > Mathieu, that's not enough. > Commit log is also wrong. > It needs to state that something like this is needed only because > changing for_each_tracepoint_range() semantics will break lttng. > I'll post a follow up patch shortly. No it does not. This is needed because I find it cleaner. If you don't want to pull this into your patch set. I'll pull it into mine. -- Steve