Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp526943pxb; Tue, 19 Oct 2021 07:47:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyWq5kFBva5YHUoDvamoUH/y0X/eg/0oRnbRUzDjdnwCQaLq2FrbZ+X1oQJMjZDZZc/Innt X-Received: by 2002:a17:906:5384:: with SMTP id g4mr37559566ejo.27.1634654869748; Tue, 19 Oct 2021 07:47:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634654869; cv=none; d=google.com; s=arc-20160816; b=oS+Rw7gb3DV3lkBrQ+lgnQQruDgoiX/U8s8B/5HtK6ClOXL9UJ+g7lGpj9dtSODdvq u0GFBMUPGBURODihRaeEAyUx9RuMKoMw3WH/3t+ev0tGsLWceqHL4pri/mafA+cOSq+s JGliG7gg9vTWdeKMO9YU9Hk2Btm631kmq15x5pl0d995VDHwpWsEoJffdZa1gvVhR5hj N0y+qWceZq+wDjukVswPcBjMx/Ik3pUTpjVHVT1GR/8PBf13hFAqCVyNgwbcAiA9F7kO iYscipwzNMaUT48iE6HmSMZD+mrG6jBkJA586ryTUU9eNx2+WPp3mWZIRw2t97XcmEt7 DNfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=XR0jya8iuYGr4qy3XH7iTTVkMxDl9/+fAXdWr/62lMw=; b=FEA8ygyRVmmLlJUy0FCjazI+7+kM2+BIS7eD1yrJxtCuTg1TbFUzxx5RacEb06JaKL JTT6OlCyYRsektI+w4hdBbDtbc+1WRwO52H3qzwJWK1vc7zLLCXSCCq1e2O7LRSt8xF5 k8T3K3cG8SbBYKM4uYOELdIYH8I3Z0DNkzXuTx9blcAA5MD0JPP5lGQCssTygq0zVeof adGKTg4Ls+OUI5GFC0shf4B1d9Xrco/HYCr1YUGT61Dx0ELVDLY4l9pjBxhDYBCjliiZ GJ/fE5t4oEP5tq+soehzoHA0v5fE33fWu165hHZNJyNd4fqksrrZwBPfero2Bl9DQ4w6 xgTw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i14si24333257eje.573.2021.10.19.07.47.20; Tue, 19 Oct 2021 07:47:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231402AbhJSOq3 convert rfc822-to-8bit (ORCPT + 99 others); Tue, 19 Oct 2021 10:46:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:42488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231441AbhJSOq2 (ORCPT ); Tue, 19 Oct 2021 10:46:28 -0400 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 24E226115A; Tue, 19 Oct 2021 14:44:15 +0000 (UTC) Date: Tue, 19 Oct 2021 10:44:11 -0400 From: Steven Rostedt To: Jiri Olsa Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, Alexei Starovoitov , Daniel Borkmann , Andrii Nakryiko Subject: Re: [PATCH 7/8] ftrace: Add multi direct modify interface Message-ID: <20211019104411.18322063@gandalf.local.home> In-Reply-To: References: <20211008091336.33616-1-jolsa@kernel.org> <20211008091336.33616-8-jolsa@kernel.org> <20211014162819.5c85618b@gandalf.local.home> <20211015100509.78d4fb01@gandalf.local.home> <20211018221015.3f145843@gandalf.local.home> <20211019093216.058ec98b@gandalf.local.home> 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=UTF-8 Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 19 Oct 2021 16:03:03 +0200 Jiri Olsa wrote: > > You can make sure the patches in there have your latest version, as you can > > review my patch. I'll update the tags if you give me one. > > I'm getting error when compiling: > > CC kernel/trace/ftrace.o > kernel/trace/ftrace.c: In function ‘modify_ftrace_direct_multi’: > kernel/trace/ftrace.c:5608:2: error: label ‘out_unlock’ defined but not used [-Werror=unused-label] Ah, I don't think I've been hit by the "-Werror" yet ;-) > 5608 | out_unlock: > | ^~~~~~~~~~ > > looks like out_unlock is nolonger needed, I removed it My tests would have found this, as it has a check for "new warnings". Anyway, was this in your latest patch, or did I pull in and older one? That is, should I expect a v2 from you? -- Steve