mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: mohitpawar@mitaoe.ac.in, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fixed: fs: file_table_c: Missing blank line warnings and struct declaration improved
Date: Mon, 29 Jul 2024 14:18:02 +0200	[thread overview]
Message-ID: <20240729-abgeordnete-attest-d20071dfb242@brauner> (raw)
In-Reply-To: <20240729114959.lxhpjhve7lhpf2jm@quack3>

On Mon, Jul 29, 2024 at 01:49:59PM GMT, Jan Kara wrote:
> On Sat 27-07-24 12:51:34, mohitpawar@mitaoe.ac.in wrote:
> > From: Mohit0404 <mohitpawar@mitaoe.ac.in>
> > 
> > Fixed-
> > 	WARNING: Missing a blank line after declarations
> > 	WARNING: Missing a blank line after declarations
> > 	Declaration format: improved struct file declaration format
> > 
> > Signed-off-by: Mohit0404 <mohitpawar@mitaoe.ac.in>
> > ---
> >  fs/file_table.c | 6 +++++-
> >  1 file changed, 5 insertions(+), 1 deletion(-)
> > 
> > diff --git a/fs/file_table.c b/fs/file_table.c
> > index ca7843dde56d..306d57623447 100644
> > --- a/fs/file_table.c
> > +++ b/fs/file_table.c
> > @@ -136,6 +136,7 @@ static int __init init_fs_stat_sysctls(void)
> >  	register_sysctl_init("fs", fs_stat_sysctls);
> >  	if (IS_ENABLED(CONFIG_BINFMT_MISC)) {
> >  		struct ctl_table_header *hdr;
> > +
> >  		hdr = register_sysctl_mount_point("fs/binfmt_misc");
> >  		kmemleak_not_leak(hdr);
> >  	}
> > @@ -383,7 +384,10 @@ EXPORT_SYMBOL_GPL(alloc_file_pseudo_noaccount);
> >  struct file *alloc_file_clone(struct file *base, int flags,
> >  				const struct file_operations *fops)
> >  {
> > -	struct file *f = alloc_file(&base->f_path, flags, fops);
> > +	struct file *f;
> > +
> > +	f = alloc_file(&base->f_path, flags, fops);
> > +
> 
> When you separated the function call from the declaration of 'f' this empty
> line is superfluous. Maybe Christian can fix it up in his tree (or maybe he
> already did). Otherwise the patch looks good. Feel free to add:

I already did. :)

      reply	other threads:[~2024-07-29 12:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-27  7:21 [Patch] Fixed-fs-file_table_c-Missing-blank-line-warnings-an.patch mohitpawar
2024-07-27  7:21 ` [PATCH] Fixed: fs: file_table_c: Missing blank line warnings and struct declaration improved mohitpawar
2024-07-29 10:57   ` Christian Brauner
2024-07-29 11:49   ` Jan Kara
2024-07-29 12: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=20240729-abgeordnete-attest-d20071dfb242@brauner \
    --to=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mohitpawar@mitaoe.ac.in \
    /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

all inboxes | Powered by JetHome®