From: Randy Dunlap <rdunlap@xenotime.net>
To: Rahul Bedarkar <rpal143@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH]: Added comments in fat.h
Date: Thu, 24 Nov 2011 10:16:53 -0800 [thread overview]
Message-ID: <4ECE8A15.2010505@xenotime.net> (raw)
In-Reply-To: <CA+NV+Vn2jq3r3VsS1pL_XEQPF5=ph3FAx2_wDGdLnCvZDFXUFQ@mail.gmail.com>
On 11/24/2011 04:46 AM, Rahul Bedarkar wrote:
> Hi,
>
> Added comments in fat.h
>
> signed off by <rpal143@gmail.com>
Improper format for Signed-off-by: line.
See Documentation/SubmittingPatches, please.
and please Cc: the FAT fs maintainer.
>
> [master b5334fc] Added comments in fat.h
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
>
> diff --git a/fs/fat/fat.h b/fs/fat/fat.h
> index 1510a4d..3b64fe0 100644
> --- a/fs/fat/fat.h
> +++ b/fs/fat/fat.h
> @@ -75,7 +75,7 @@ struct msdos_sb_info {
> struct fat_mount_options options;
> struct nls_table *nls_disk; /* Codepage used on disk */
> struct nls_table *nls_io; /* Charset used for input and display */
> - const void *dir_ops; /* Opaque; default
> directory operations */
Your email client incorrectly split the above source line into 2 lines.
Maybe Documentation/email-clients.txt can help you.
> + const void *dir_ops; /* Opaque; default directory operations */
> int dir_per_block; /* dir entries per block */
> int dir_per_block_bits; /* log2(dir_per_block) */
>
> @@ -179,6 +179,7 @@ static inline u8 fat_make_attrs(struct inode *inode)
> return attrs;
> }
>
> +/* Sets the FAT attribute byte for thid inode */
thid should be third? or this?
> static inline void fat_save_attrs(struct inode *inode, u8 attrs)
> {
> if (fat_mode_can_hold_ro(inode))
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2011-11-24 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 12:46 [PATCH]: Added comments in fat.h Rahul Bedarkar
2011-11-24 18:16 ` Randy Dunlap [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=4ECE8A15.2010505@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rpal143@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