From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/7] docs/mm: make GFP flags descriptions usable as kernel-doc
Date: Fri, 27 Jul 2018 15:29:32 -0600 [thread overview]
Message-ID: <20180727152932.0ead76d1@lwn.net> (raw)
In-Reply-To: <20180727212720.GD17745@rapoport-lnx>
On Sat, 28 Jul 2018 00:27:21 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> > I won't insist on this, but I would suggest that, in this particular case,
> > it might be better for that markup to come out.
>
> No problem with removing % signs, but the whitespace changes are necessary,
> otherwise the generated html gets weird.
The whitespace changes are fine - it's really just the % markup I was
commenting on.
Thanks,
jon
next prev parent reply other threads:[~2018-07-27 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 17:32 [PATCH v3 0/7] memory management documentation updates Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 1/7] mm/util: make strndup_user description a kernel-doc comment Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 2/7] mm/util: add kernel-doc for kvfree Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 3/7] docs/core-api: kill trailing whitespace in kernel-api.rst Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 4/7] docs/core-api: move *{str,mem}dup* to "String Manipulation" Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 5/7] docs/core-api: split memory management API to a separate file Mike Rapoport
2018-07-26 17:32 ` [PATCH v3 6/7] docs/mm: make GFP flags descriptions usable as kernel-doc Mike Rapoport
2018-07-26 22:08 ` Jonathan Corbet
2018-07-27 21:27 ` Mike Rapoport
2018-07-27 21:29 ` Jonathan Corbet [this message]
2018-07-26 17:32 ` [PATCH v3 7/7] docs/core-api: mm-api: add section about GFP flags Mike Rapoport
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=20180727152932.0ead76d1@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=willy@infradead.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).