Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Christian Brauner <brauner@kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	llvm@lists.linux.dev, Jan Kara <jack@suse.cz>,
	Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>
Subject: Re: [PATCH v1 1/1] lock_mount(): Remove unused function
Date: Tue, 16 Sep 2025 02:25:37 +0100	[thread overview]
Message-ID: <20250916012537.GL39973@ZenIV> (raw)
In-Reply-To: <20250915160221.2916038-1-andriy.shevchenko@linux.intel.com>

On Mon, Sep 15, 2025 at 06:02:21PM +0200, Andy Shevchenko wrote:
> clang is not happy about unused function:
> 
> /fs/namespace.c:2856:20: error: unused function 'lock_mount' [-Werror,-Wunused-function]
>  2856 | static inline void lock_mount(const struct path *path,
>       |                    ^~~~~~~~~~
> 1 error generated.
> 
> Fix the compilation breakage (`make W=1` build) by removing unused function.
> 
> Fixes: d14b32629541 ("change calling conventions for lock_mount() et.al.")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

Folded into commit in question to avoid bisect hazard

  reply	other threads:[~2025-09-16  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 16:02 [PATCH v1 1/1] lock_mount(): Remove unused function Andy Shevchenko
2025-09-16  1:25 ` Al Viro [this message]
2025-09-16 11:17   ` Andy Shevchenko
2025-09-16 12:37     ` Andy Shevchenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250916012537.GL39973@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=justinstitt@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox