From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH 2/2] debugfs: log errors when something goes wrong
Date: Wed, 3 Jul 2019 12:43:08 +0100 [thread overview]
Message-ID: <20190703114308.GU2793@sirena.org.uk> (raw)
In-Reply-To: <20190703071653.2799-2-gregkh@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Wed, Jul 03, 2019 at 09:16:53AM +0200, Greg Kroah-Hartman wrote:
> As it is not recommended that debugfs calls be checked, it was pointed
> out that major errors should still be logged somewhere so that
> developers and users have a chance to figure out what went wrong. To
> help with this, error logging has been added to the debugfs core so that
> it is not needed to be present in every individual file that calls
> debugfs.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-03 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 7:16 [PATCH 1/2] debugfs: provide pr_fmt() macro Greg Kroah-Hartman
2019-07-03 7:16 ` [PATCH 2/2] debugfs: log errors when something goes wrong Greg Kroah-Hartman
2019-07-03 9:10 ` Rafael J. Wysocki
2019-07-03 9:32 ` Greg Kroah-Hartman
2019-07-03 9:35 ` Takashi Iwai
2019-07-03 14:53 ` Greg Kroah-Hartman
2019-07-03 9:37 ` Rafael J. Wysocki
2019-07-03 11:43 ` Mark Brown [this message]
2019-07-03 9:09 ` [PATCH 1/2] debugfs: provide pr_fmt() macro Rafael J. Wysocki
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=20190703114308.GU2793@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tiwai@suse.de \
/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
Powered by JetHome