From: Greg KH <greg@kroah.com>
To: Bao Zhao <baozhaolinuxer@yahoo.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: typo in debugfs code comments?
Date: Fri, 9 Dec 2005 18:57:21 -0800 [thread overview]
Message-ID: <20051210025720.GA17847@kroah.com> (raw)
In-Reply-To: <20051210020134.94755.qmail@web31712.mail.mud.yahoo.com>
On Fri, Dec 09, 2005 at 06:01:34PM -0800, Bao Zhao wrote:
> I think that the comments of debugfs_create_u16 and
> debugfs_create_u32
> have the copy and paste error.
>
> below is original comments.
> /**
> * debugfs_create_u16 - create a file in the debugfs
> filesystem that is used to read and write a unsigned 8
> bit value.
> *
>
> /**
> * debugfs_create_u32 - create a file in the debugfs
> filesystem that is used to read and write a unsigned 8
> bit value.
> *
>
> It should be "a unsigned 16 bit value" and "a unsigned
> 32 bit value"
Heh, cut and paste comments :)
Care to send me a patch, as per Documentation/SubmittingPatches to fix
this up?
thanks,
greg k-h
next prev parent reply other threads:[~2005-12-10 4:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 2:01 typo in debugfs code comments? Bao Zhao
2005-12-10 2:57 ` Greg KH [this message]
2005-12-10 7:50 ` Bao Zhao
2005-12-10 8:18 ` 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=20051210025720.GA17847@kroah.com \
--to=greg@kroah.com \
--cc=baozhaolinuxer@yahoo.com \
--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 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.