From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] debugfs: make error message a bit more verbose
Date: Sat, 6 Jul 2019 16:53:43 +0100 [thread overview]
Message-ID: <20190706155343.GI20625@sirena.org.uk> (raw)
In-Reply-To: <20190706154256.GA2683@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 378 bytes --]
On Sat, Jul 06, 2019 at 05:42:56PM +0200, Greg Kroah-Hartman wrote:
> When a file/directory is already present in debugfs, and it is attempted
> to be created again, be more specific about what file/directory is being
> created and where it is trying to be created to give a bit more help to
> developers to figure out the problem.
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-07-06 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 15:42 [PATCH] debugfs: make error message a bit more verbose Greg Kroah-Hartman
2019-07-06 15:53 ` Mark Brown [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=20190706155343.GI20625@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sfr@canb.auug.org.au \
--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 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.