linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: linux-mm@kvack.org, Dave Hansen <dave.hansen@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: add comments on pglist_data zones
Date: Thu, 21 May 2020 04:45:06 -0700	[thread overview]
Message-ID: <20200521114506.GB28818@bombadil.infradead.org> (raw)
In-Reply-To: <20200521045300.vh2ukn63rr423q4n@intel.com>

On Wed, May 20, 2020 at 09:53:00PM -0700, Ben Widawsky wrote:
> On 20-05-20 16:22:35, Matthew Wilcox wrote:
> > On Wed, May 20, 2020 at 01:54:43PM -0700, Ben Widawsky wrote:
> > > While making other modifications it was easy to confuse the two struct
> > > members node_zones and node_zonelists. For those already familiar with
> > > the code, this might seem to be a silly patch, but it's quite helpful to
> > > disambiguate the similar-sounding fields
> > > 
> > > While here, add a small comment on why nr_zones isn't simply MAX_NR_ZONES
> > 
> > It seems like a real shame to write all this excellent documentation
> > and not format it as kernel-doc.
> 
> I admit, I didn't look at all the kernel-doc files. Is there precedent there for
> documenting struct members like this? I'd be more than happy to try to document
> everything I've dug up in coming up to speed here. 
> 
> I've used the docs from Mel quite a bit and would very much like to pay it
> forward, as it were.

I appreciate your willingness!  Fortunately, we have excellent
documentation on adding more documentation ;-)

Documentation/doc-guide/kernel-doc.rst is where you'll want to start.
'Structure, union, and enumeration documentation' is the section.
Do read through the whole section before jumping in because you might
find it more clear to use the style in 'In-line member documentation
comments' rather than the style documented first.


      reply	other threads:[~2020-05-21 11:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 20:54 Ben Widawsky
2020-05-20 23:22 ` Matthew Wilcox
2020-05-21  4:53   ` Ben Widawsky
2020-05-21 11:45     ` Matthew Wilcox [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=20200521114506.GB28818@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-mm@kvack.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