From: Linus Walleij <linus.walleij@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] mfd: ab8500: no need to check return value of debugfs_create functions
Date: Mon, 29 Jul 2019 00:22:19 +0200 [thread overview]
Message-ID: <CACRpkdbBXoTywAXb-18LJkTFayLgdRhrxEq0DoJxpCkn=Etupw@mail.gmail.com> (raw)
In-Reply-To: <20190706164722.18766-2-gregkh@linuxfoundation.org>
On Sat, Jul 6, 2019 at 6:48 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> 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: Linus Walleij <linus.walleij@linaro.org>
> Cc: Lee Jones <lee.jones@linaro.org>
> Cc: linux-arm-kernel@lists.infradead.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-07-28 22:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 16:47 [PATCH 1/3] mfd: ab3100: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-07-06 16:47 ` [PATCH 2/3] mfd: ab8500: " Greg Kroah-Hartman
2019-07-28 22:22 ` Linus Walleij [this message]
2019-08-08 7:32 ` Lee Jones
2019-07-06 16:47 ` [PATCH 3/3] mfd: aat2870: " Greg Kroah-Hartman
2019-08-08 7:32 ` Lee Jones
2019-07-28 22:21 ` [PATCH 1/3] mfd: ab3100: " Linus Walleij
2019-08-08 7:32 ` Lee Jones
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='CACRpkdbBXoTywAXb-18LJkTFayLgdRhrxEq0DoJxpCkn=Etupw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 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).