linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tobin C. Harding" <me@tobin.cc>
To: Jan Kara <jack@suse.cz>
Cc: Theodore Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jbd2: fix sphinx kerel-doc build warnings for journal_s
Date: Tue, 9 Jan 2018 07:32:43 +1100	[thread overview]
Message-ID: <20180108203243.GB2462@eros> (raw)
In-Reply-To: <20180108151604.v4kfq47dc4cpcdxw@quack2.suse.cz>

On Mon, Jan 08, 2018 at 04:16:04PM +0100, Jan Kara wrote:
> On Sun 07-01-18 11:46:14, Tobin C. Harding wrote:
> > Sphinx emits various warnings when building make target 'htmldocs'.
> > 
> > Currently struct journal_s definition contains duplicate documentation,
> > some as kernel-docs and some as standard c89 comments.  We can reduce
> > duplication while cleaning up the kernel-docs. 
> > 
> > Move all kernel-docs to right above each struct member.  Use the set of
> > all existing comments (kernel-doc and c89).
> > 
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> 
> This is probably better than having documentation in two places so:
> 
> Acked-by: Jan Kara <jack@suse.cz>
> 
> Just one nit below:
> 
> >  struct journal_s
> >  {
> > -	/* General journaling state flags [j_state_lock] */
> > +	/**
> > +	 * @j_flags:
> > +	 *
> > +	 * General journaling state flags [j_state_lock]
> > +	 */
> 
> Won't it be possible in cases like this to fold the name and description
> into one line? Like:
> 
> 	/**
> 	 * @j_flags: General journaling state flags [j_state_lock]
> 	 */
> 
> That would save a lot of vertical space...

Oh that looks much nicer. I'll have another play with it and re-spin. 

thanks,
Tobin.

      reply	other threads:[~2018-01-08 20:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07  0:46 [PATCH] jbd2: fix sphinx kerel-doc build warnings for journal_s Tobin C. Harding
2018-01-08 15:16 ` Jan Kara
2018-01-08 20:32   ` Tobin C. Harding [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=20180108203243.GB2462@eros \
    --to=me@tobin.cc \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).