From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH debugfs: implement symbolic links
Date: Wed, 14 Feb 2007 07:42:08 +0100 [thread overview]
Message-ID: <20070214074208.0e2d1724@gondolin.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20070214013142.GB9023@suse.de>
On Tue, 13 Feb 2007 17:31:42 -0800,
Greg KH <gregkh@suse.de> wrote:
> > That makes it easy to get return code checking wrong (especially
> > considering the comment above), and a number of callers do get it wrong.
>
> They do?
For example, fs/ocfs2/super.c only checks for NULL (while neither
selecting nor depending on debugfs), or drivers/block/pktcdvd.c will
only check for IS_ERR(). (Many callers don't seem to care about return
codes at all.)
> The goal here is not to force the caller to care if debugfs is enabled
> or not.
And that's definetly a good thing. (Looking again, not checking for
IS_ERR() isn't as bad as I thought, as the code will continue to do
nothing if called again for a non-existing dentry.)
> > At the very least we should change the misleading comment.
>
> agreed, patches always welcome :)
OK, just changing the comment looks like the most sensible thing to do.
I'll roll up a patch.
next prev parent reply other threads:[~2007-02-14 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 11:13 Peter Oberparleiter
2007-02-13 15:45 ` Cornelia Huck
2007-02-14 1:31 ` Greg KH
2007-02-14 6:42 ` Cornelia Huck [this message]
2007-02-14 6:57 ` [Patch] debugfs: Remove misleading comments Cornelia Huck
2007-02-14 1:27 ` [PATCH debugfs: implement symbolic links Greg KH
2007-02-14 8:03 ` Peter 1 Oberparleiter
2007-02-14 19:45 ` Greg KH
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=20070214074208.0e2d1724@gondolin.boeblingen.de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.oberparleiter@de.ibm.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
all inboxes | Powered by JetHome®