Linux filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jan Kara <jack@suse.cz>, Al Viro <viro@zeniv.linux.org.uk>,
	David Howells <dhowells@redhat.com>,
	Aleksa Sarai <cyphar@cyphar.com>, Karel Zak <kzak@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] super: remove get_tree_single_reconf()
Date: Wed, 2 Aug 2023 09:20:28 +0200	[thread overview]
Message-ID: <20230802-zettel-krempel-7094d4718ab1@brauner> (raw)
In-Reply-To: <20230801153100.GB12035@lst.de>

On Tue, Aug 01, 2023 at 05:31:00PM +0200, Christoph Hellwig wrote:
> On Tue, Aug 01, 2023 at 03:09:00PM +0200, Christian Brauner wrote:
> > The get_tree_single_reconf() helper isn't used anywhere. Remote it.
> 
> Yeah, I've got pretty much the same patch hiding somewhere in one of
> me trees..
> 
> > -static int vfs_get_super(struct fs_context *fc, bool reconf,
> > -		int (*test)(struct super_block *, struct fs_context *),
> > -		int (*fill_super)(struct super_block *sb,
> > -				  struct fs_context *fc))
> > +static int vfs_get_super(struct fs_context *fc,
> > +			 int (*test)(struct super_block *, struct fs_context *),
> > +			 int (*fill_super)(struct super_block *sb,
> > +					   struct fs_context *fc))
> 
> .a althought keeping the existing formatting here seems much more readable
> to me.  No idea why the odd align to brace formatting has picked up so
> many fans recently given that it is horrible to read and causes tons
> of churn when touching the protoptype or function name.

I'm not doing that manually. I'm using clang-format for this so I don't
have to care about stuff like this.

Tbh, the fact that we don't simply have an authoritative code formatting
tool in-kernel over 30 years later that we settle on - at least on a per
subsystem basis - is funny and sad.

I'm fine not touching the header.

  reply	other threads:[~2023-08-02  7:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 13:08 [PATCH RFC 0/3] fs: allow userspace to detect superblock reuse Christian Brauner
2023-08-01 13:09 ` [PATCH RFC 1/3] super: remove get_tree_single_reconf() Christian Brauner
2023-08-01 15:31   ` Christoph Hellwig
2023-08-02  7:20     ` Christian Brauner [this message]
2023-08-02 16:49   ` Jan Kara
2023-08-01 13:09 ` [PATCH RFC 2/3] fs: add vfs_cmd_create() Christian Brauner
2023-08-01 15:43   ` Christoph Hellwig
2023-08-01 15:48     ` Christoph Hellwig
2023-08-02  8:02     ` Christian Brauner
2023-08-02 17:01   ` Jan Kara
2023-08-02 17:13     ` Jan Kara
2023-08-01 13:09 ` [PATCH RFC 3/3] fs: add FSCONFIG_CMD_CREATE_EXCL Christian Brauner
2023-08-01 15:46   ` Christoph Hellwig
2023-08-02  7:38     ` Christian Brauner
2023-08-01 14:25 ` [PATCH RFC 0/3] fs: allow userspace to detect superblock reuse Josef Bacik
2023-08-02  7:49   ` Christian Brauner

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=20230802-zettel-krempel-7094d4718ab1@brauner \
    --to=brauner@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@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