linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Christian Brauner <brauner@kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 1/2] fs: d_path: include internal.h
Date: Wed, 17 May 2023 09:18:59 +0200	[thread overview]
Message-ID: <20230517-ratten-bezeichnen-ad20e1d5f60f@brauner> (raw)
In-Reply-To: <20230516195444.551461-1-arnd@kernel.org>

On Tue, 16 May 2023 21:54:38 +0200, Arnd Bergmann wrote:
> make W=1 warns about a missing prototype that is defined but
> not visible at point where simple_dname() is defined:
> 
> fs/d_path.c:317:7: error: no previous prototype for 'simple_dname' [-Werror=missing-prototypes]
> 
> 

Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc

[1/2] fs: d_path: include internal.h
      https://git.kernel.org/vfs/vfs/c/fb385a13fc9a
[2/2] fs: pipe: reveal missing function protoypes
      https://git.kernel.org/vfs/vfs/c/bf0603ebb9ee

      parent reply	other threads:[~2023-05-17  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 19:54 [PATCH 1/2] fs: d_path: include internal.h Arnd Bergmann
2023-05-16 19:56 ` [PATCH 2/2] fs: pipe: reveal missing function protoypes Arnd Bergmann
2023-05-17  7:18 ` Christian Brauner [this message]

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=20230517-ratten-bezeichnen-ad20e1d5f60f@brauner \
    --to=brauner@kernel.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).