From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: cleancache: no need to check return value of debugfs_create functions
Date: Wed, 23 Jan 2019 09:25:07 -0500 [thread overview]
Message-ID: <20190123142504.GA19985@Konrads-MacBook-Pro.local> (raw)
In-Reply-To: <20190122152151.16139-12-gregkh@linuxfoundation.org>
On Tue, Jan 22, 2019 at 04:21:11PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
OK.
Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
or I can push it through my tree but it may be just easier for Andrew
too do it
> Cc: linux-mm@kvack.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> mm/cleancache.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/mm/cleancache.c b/mm/cleancache.c
> index 2bf12da9baa0..082fdda7aaa6 100644
> --- a/mm/cleancache.c
> +++ b/mm/cleancache.c
> @@ -305,8 +305,7 @@ static int __init init_cleancache(void)
> {
> #ifdef CONFIG_DEBUG_FS
> struct dentry *root = debugfs_create_dir("cleancache", NULL);
> - if (root == NULL)
> - return -ENXIO;
> +
> debugfs_create_u64("succ_gets", 0444, root, &cleancache_succ_gets);
> debugfs_create_u64("failed_gets", 0444, root, &cleancache_failed_gets);
> debugfs_create_u64("puts", 0444, root, &cleancache_puts);
> --
> 2.20.1
>
prev parent reply other threads:[~2019-01-23 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:21 [PATCH] mm: cleancache: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-23 14:25 ` Konrad Rzeszutek Wilk [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=20190123142504.GA19985@Konrads-MacBook-Pro.local \
--to=konrad.wilk@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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).