linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Dave Chinner <david@fromorbit.com>, Luis Chamberlain <mcgrof@kernel.org>
Cc: jake@lwn.net, hch@infradead.org, djwong@kernel.org,
	dchinner@redhat.com, ritesh.list@gmail.com, rgoldwyn@suse.com,
	jack@suse.cz, linux-doc@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org, p.raghav@samsung.com,
	da.gomez@samsung.com, rohan.puri@samsung.com
Subject: Re: [PATCH v2] Documentation: add initial iomap kdoc
Date: Fri, 19 May 2023 06:41:06 -0600	[thread overview]
Message-ID: <87r0rcpk7x.fsf@meer.lwn.net> (raw)
In-Reply-To: <ZGbVaewzcCysclPt@dread.disaster.area>

Dave Chinner <david@fromorbit.com> writes:

One little point among all the more substantial stuff:

>> -/*
>> - * Types of block ranges for iomap mappings:
>> +/**
>> + * DOC: iomap block ranges types
>
> I seriously dislike this "DOC:" keyword appearing everywhere.
> We've already got a "this is a comment for documentation" annotation
> in the "/**" comment prefix, having to add "DOC:" is entirely
> redudant and unnecessary noise.

DOC: actually isn't redundant, it causes the kernel-doc directive to
pull that text into the rendered documentation.

This document shows both the advantages and disadvantages of that
mechanism, IMO.  It allows the documentation to be kept with the code,
where optimistic people think it is more likely to be updated.  But it
also scatters the material to the detriment of readers of the plain-text
documentation.  The rendered version of iomap.rst is rather more
complete and comprehensible than the RST file itself.

Thanks,

jon

  reply	other threads:[~2023-05-19 12:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 15:01 [PATCH v2] Documentation: add initial iomap kdoc Luis Chamberlain
2023-05-18 15:49 ` Randy Dunlap
2023-05-18 20:55   ` Luis Chamberlain
2023-05-18 23:09 ` Jonathan Corbet
2023-05-19  1:48 ` Dave Chinner
2023-05-19 12:41   ` Jonathan Corbet [this message]
2023-05-19  5:04 ` Christoph Hellwig
2023-05-23  1:20   ` Darrick J. Wong
2023-05-23  2:11     ` Randy Dunlap

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=87r0rcpk7x.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=da.gomez@samsung.com \
    --cc=david@fromorbit.com \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jake@lwn.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=rgoldwyn@suse.com \
    --cc=ritesh.list@gmail.com \
    --cc=rohan.puri@samsung.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;
as well as URLs for NNTP newsgroup(s).