From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] f2fs: adjust kernel coding style
Date: Mon, 10 Dec 2012 14:15:30 +0900 [thread overview]
Message-ID: <1355116530.7291.69.camel@kjgkr> (raw)
In-Reply-To: <alpine.LNX.2.01.1212100422580.25777@nerf07.vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 686 bytes --]
2012-12-10 (월), 04:24 +0100, Jan Engelhardt:
> On Thursday 2012-11-29 05:38, Jaegeuk Kim wrote:
>
> >As pointed out by Randy Dunlap, this patch removes all usage of "/**" for comment
> >blocks. Instead, just use "/*".
>
> /** is correct for comments describing the function/struct.
Yes, right.
But, as you see the context covered by "/**" below, IMO, those are just
for comments, not for making kernel-docs.
If we need kernel-docs, additional works should be done later.
Thanks,
>
> >-/**
> >+/*
> > * We guarantee no failure on the returned page.
> > */
> > struct page *grab_meta_page(struct f2fs_sb_info *sbi, pgoff_t index)
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-12-10 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 4:38 [PATCH] f2fs: adjust kernel coding style Jaegeuk Kim
2012-12-10 3:24 ` Jan Engelhardt
2012-12-10 5:15 ` Jaegeuk Kim [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=1355116530.7291.69.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=jengelh@inai.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).