All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] debugfs: remove return value of debugfs_create_bool()
Date: Mon, 24 May 2021 14:39:18 +0200	[thread overview]
Message-ID: <YKuedipmEjIW91Jr@kroah.com> (raw)
In-Reply-To: <CAMuHMdXbSyresZNUqq-g4=HNFXqtj2QkPpN1s0LRjmOnNPxn8w@mail.gmail.com>

On Mon, May 24, 2021 at 01:44:38PM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
> 
> On Mon, May 24, 2021 at 12:18 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Mon, May 24, 2021 at 11:51:42AM +0200, Geert Uytterhoeven wrote:
> > > On Mon, May 24, 2021 at 11:41 AM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > > On Mon, May 24, 2021 at 11:11:32AM +0200, Geert Uytterhoeven wrote:
> > > > > On Fri, May 21, 2021 at 10:28 PM Greg Kroah-Hartman
> > > > > <gregkh@linuxfoundation.org> wrote:
> > > > > > No one checks the return value of debugfs_create_bool(), as it's not
> > > > > > needed, so make the return value void, so that no one tries to do so in
> > > > >
> > > > > Please explain in the patch description why it is not needed.
> > > >
> > > > Because you just do not need it, like almost all other debugfs calls
> > > > now.
> > >
> > > Why do I just not need it?
> >
> > Let me flip it around, why do you need it?  There are no in-kernel users
> > of the return value anymore so what code requires this pointer now?
> 
> There still are a few users of other members in the family, and some
> of them are meant to be removed without removing the full parent
> directory.  Having all debugfs_create_*() functions behave the same
> is a bonus.

I agree, and we are almost there, all that is left is:
	debugfs_create_blob()
	debugfs_create_file()
	debugfs_create_file_unsafe()
for creating debugfs files.

There is still:
	debugfs_create_dir()
	debugfs_create_symlink()
	debugfs_create_automount()
for non-file creations that do not return void.

The majority of the debugfs_create_* functions now do not return
anything.

> But if other people are fine with having to call
> debugfs_remove(debugfs_lookup(...)), well, let it be like that...

It saves at least a static variable, so what's not to like?  :)

thanks,

greg k-h

  reply	other threads:[~2021-05-24 12:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 18:45 [PATCH] debugfs: remove return value of debugfs_create_bool() Greg Kroah-Hartman
2021-05-24  9:11 ` Geert Uytterhoeven
2021-05-24  9:41   ` Greg Kroah-Hartman
2021-05-24  9:51     ` Geert Uytterhoeven
2021-05-24 10:18       ` Greg Kroah-Hartman
2021-05-24 11:44         ` Geert Uytterhoeven
2021-05-24 12:39           ` Greg Kroah-Hartman [this message]
2021-05-25  7:26             ` Geert Uytterhoeven
2021-05-25  7:48               ` Greg Kroah-Hartman

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=YKuedipmEjIW91Jr@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.