From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sasikantha babu <sasikanth.v19@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs: New debugfs interface for creation of files, directory and symlinks
Date: Wed, 2 May 2012 08:31:00 -0700 [thread overview]
Message-ID: <20120502153100.GA2777@kroah.com> (raw)
In-Reply-To: <1335963054-24750-1-git-send-email-sasikanth.v19@gmail.com>
On Wed, May 02, 2012 at 06:20:54PM +0530, Sasikantha babu wrote:
> As we know the current debugfs file or directory or symlink creation
> doesn't return proper error codes to the caller on failure. Because
> of this caller and user could not able to find the exact reason of
> the failure.
And what is the problem with this? Either the file is created or not,
you really shouldn't care anymore than that. It's not like you are
going to retry the creation, or are you?
Who really cares if the file is failed to be created?
> As Andrew Morton suggested (http://www.spinics.net/lists/linux-mm/msg33617.html)
> introduced new debugfs interface to create debugfs entries. Newer APIs
> returns proper error codes(ERR_PTR) on failure.
Again, why? What root problem are you trying to solve here?
thanks,
greg k-h
next prev parent reply other threads:[~2012-05-02 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 12:50 [PATCH] debugfs: New debugfs interface for creation of files, directory and symlinks Sasikantha babu
2012-05-02 15:31 ` Greg Kroah-Hartman [this message]
2012-05-02 21:58 ` Sasikanth babu
2012-05-02 22:04 ` Greg Kroah-Hartman
2012-05-02 22:20 ` Andrew Morton
2012-05-02 22:36 ` Greg Kroah-Hartman
2012-05-02 22:44 ` Andrew Morton
2012-05-02 23:07 ` 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=20120502153100.GA2777@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasikanth.v19@gmail.com \
/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