Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1504335pxb; Mon, 22 Feb 2021 03:50:41 -0800 (PST) X-Google-Smtp-Source: ABdhPJx25epkdQc5+G2uBY/4hIeHNvac6hMj+35lC48pnpZxfTe3KJeYZbhIfrmjzQWm8l20Eqd7 X-Received: by 2002:a50:fa91:: with SMTP id w17mr21685533edr.195.1613994641339; Mon, 22 Feb 2021 03:50:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1613994641; cv=none; d=google.com; s=arc-20160816; b=E//1y8OrbWGeoYLOY61PiJmQsopJyrF3glBMFxICfCLqdUBQkB90/uBU40OHES26pa T83mUXMPA21iOCDqfamqryE32c/YlLOAG+XJY5FCUHffrdvl1EKICKFXrmuQRFELEAmj FTFIQruIc7LLn8xbzeCGX9DSQOSuCjZpk4GN+jYFFHqWIXgDg/0rpI3bRLTC75m6HZ6p veNCniSvHbQCWZdfJcZNSG8NazpDC/72PcTmbqYHgrFDYzp3qgGpaVLGXZ9Fx8Xkj178 ltYU2p6HBqeJY6P0wg9mH5ZGspiHNCrIbI0l5uxTuyhEcye+N4vXD7OFHpzUfa63IXKV 4+HQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version; bh=rWXicDkREDTw+ykEQDylWV5wmgHJki0d6kE6syUmwz8=; b=lpmrc1StXSXktt0BAD/fH2CF+X+xE4B/Qu5WZZbEtNb0NeCCPGIeEh/5szC5K8rKFx BASJThUxFeHcXq/uoyWpAsF41sx64STnwE3UMOqcdlV7lJ7oHEOU1tVvDdFKYpVah4+/ uh8swdfSzdeNxCMAI76086rY+3ESK99pvwsbiKmUFAtjSfB6zAD7Yx0Wch6TUIVxSWxA 1ptCtD6VB1A9E0s92lK+jzfpGAnxTSm+nZKSzS9WDf2uiwGa5+SABfuLLEByKtRj5wkR Wfuo4da3ai2ujO0eELMDXOQyJG4v9VjdjqCM3oEVwj+z5y4Ni3B5iJq+Xudj00BzFO9K G14Q== 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 h19si11557677eji.32.2021.02.22.03.50.18; Mon, 22 Feb 2021 03:50:41 -0800 (PST) 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 S229915AbhBVLsc convert rfc822-to-8bit (ORCPT + 99 others); Mon, 22 Feb 2021 06:48:32 -0500 Received: from mail-oi1-f172.google.com ([209.85.167.172]:38507 "EHLO mail-oi1-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230100AbhBVLr6 (ORCPT ); Mon, 22 Feb 2021 06:47:58 -0500 Received: by mail-oi1-f172.google.com with SMTP id h17so13641742oih.5; Mon, 22 Feb 2021 03:47:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=QlRAo98CEFZQCRMmvelMsodp72v9s50sbgzKV8vA1BA=; b=s4Wp74jJShsEbW9Bk1W7UEHgpzAhggZd/vaDpDvaibZfrjhOOzE6NYVgkzJuSzs0d+ q/Ho/MBY4slWMNo/Mh5NEWrnzm+aeMvhQ9dlm2wI3C5DhnN1WdFQl4CU/5yjy35L0cku tkyz6nGMAS+uDIznqD46DGylgsZvkAfzNIuD1R6Ysiakk8VNbA2aPQ2KNZqYOZlhmtOV K4uBbU+Nf6jL9Rze4goZMg4bupgIo1fRpZK0iJGq595XWrvS2fYpGVipfNGDnHfv+EWF nVr16LCn4m8bgksULK6u1o9iiKWzlbVohKdmnOFej5Jr6Mj7eEpxTcI2WRFLZ4K4IYmj COAw== X-Gm-Message-State: AOAM5307SzUnsy7tO8zlpSicpvku/N7nwgdsB9scLU4p78+yl+czvgRu /ESRgVe8Pv3Ba8mr8xDB9e5spD4dxpil4HTA84s= X-Received: by 2002:aca:744:: with SMTP id 65mr15128930oih.153.1613994437678; Mon, 22 Feb 2021 03:47:17 -0800 (PST) MIME-Version: 1.0 References: <20210219065417.1834-1-rdunlap@infradead.org> In-Reply-To: <20210219065417.1834-1-rdunlap@infradead.org> From: Geert Uytterhoeven Date: Mon, 22 Feb 2021 12:47:06 +0100 Message-ID: Subject: Re: [PATCH] btrfs: ref-verify: use 'inline void' keyword ordering To: Randy Dunlap Cc: Linux Kernel Mailing List , Josef Bacik , David Sterba , Chris Mason , linux-btrfs , Andrew Morton Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 19, 2021 at 7:57 AM Randy Dunlap wrote: > Fix build warnings of function signature when CONFIG_STACKTRACE is not > enabled by reordering the 'inline' and 'void' keywords. > > ../fs/btrfs/ref-verify.c:221:1: warning: ‘inline’ is not at beginning of declaration [-Wold-style-declaration] > static void inline __save_stack_trace(struct ref_action *ra) > ../fs/btrfs/ref-verify.c:225:1: warning: ‘inline’ is not at beginning of declaration [-Wold-style-declaration] > static void inline __print_stack_trace(struct btrfs_fs_info *fs_info, > > Fixes: fd708b81d972 ("Btrfs: add a extent ref verify tool") > Signed-off-by: Randy Dunlap > Cc: Josef Bacik > Cc: David Sterba > Cc: Chris Mason > Cc: linux-btrfs@vger.kernel.org > Cc: Andrew Morton > --- > Found in mmotm; applies to mainline. Thanks, fixes the warning in mainline for me. Acked-by: Geert Uytterhoeven Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds