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=-12.5 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 5D899C07E95 for ; Tue, 20 Jul 2021 19:20:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3521B610F7 for ; Tue, 20 Jul 2021 19:20:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231496AbhGTSjr (ORCPT ); Tue, 20 Jul 2021 14:39:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:39388 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231439AbhGTSik (ORCPT ); Tue, 20 Jul 2021 14:38:40 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 84A5760FF2 for ; Tue, 20 Jul 2021 19:19:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1626808758; bh=ekEnSV9ZmSGhjal9qG0LZOxeTSsU1nfka+A/MMmR0FI=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Y6iDVoaZdLsFSpqS+YFuA77dTYi0rgbFroI6RNmfjGWwcXi5GvRXzuSlrjF6h+lcz levlSVSSthqeqeGyk53aGUqlQBORn59plSqPbc2XgaHd6ZqovLlBcA0zGWxTzv7zev hDZJiqvRFaSRDMoSHhx+cPVr8Ud99WBYBPyHaUQFMvD5f+kzjRYktkp4uglro7jXp1 4kjOn6vnOWHT9PLK/iJs+3zthi0P8bTJn+Go6+IYqnlsjqinQzuX5BAEEbojualcKF 5AJWELU0mpnnZZladoE7LkDIfmpanP5tlNbRpLO3BLiQ2vufkPjhGNInuUSrRLRpaC 7AuqpaVMwd1oQ== Received: by mail-wr1-f43.google.com with SMTP id f17so27177929wrt.6 for ; Tue, 20 Jul 2021 12:19:18 -0700 (PDT) X-Gm-Message-State: AOAM533rP05DvKJ1EXw19IRlkRk2lxy2bUbESTWp55+EK4M/veTCH0VX T4ayAn8hcnXukMqWTG1J4Lr5im2nYA+JWoK5yTI= X-Google-Smtp-Source: ABdhPJwLsIlSzNXoHGHbPM0LbJfaXpfRrLGnxPrv4tF7po0cMh1HRmNRvICJKpig76DaAl1pJrFGmz8P4eJex59tnSM= X-Received: by 2002:a5d:438c:: with SMTP id i12mr38197403wrq.99.1626808757173; Tue, 20 Jul 2021 12:19:17 -0700 (PDT) MIME-Version: 1.0 References: <20210626130404.033700863@goodmis.org> <20210626130538.003082428@goodmis.org> In-Reply-To: <20210626130538.003082428@goodmis.org> From: Arnd Bergmann Date: Tue, 20 Jul 2021 21:19:01 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [for-next][PATCH 19/24] tracing: Add LATENCY_FS_NOTIFY to define if latency_fsnotify() is defined To: Steven Rostedt Cc: Linux Kernel Mailing List , Ingo Molnar , Andrew Morton , kernel test robot Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jun 26, 2021 at 3:10 PM Steven Rostedt wrote: > > From: "Steven Rostedt (VMware)" > > With the coming addition of the osnoise tracer, the configs needed to > include the latency_fsnotify() has become more complex, and to keep the > declaration in the header file the same as in the C file, just have the > logic needed to define it in one place, and that defines LATENCY_FS_NOTIFY > which will be used in the C code. > > Reported-by: kernel test robot > Signed-off-by: Steven Rostedt (VMware) This still doesn't seem quite right. I just came across this randconfig build warning on 5.14-rc2: kernel/trace/trace.c:1712:13: error: 'trace_create_maxlat_file' defined but not used [-Werror=unused-function] 1712 | static void trace_create_maxlat_file(struct trace_array *tr, See https://pastebin.com/raw/b3DH7hWg for the .config that triggered it. Arnd