From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/memblock: fix typo in memblock doc
Date: Thu, 12 Sep 2019 20:29:47 +0800 [thread overview]
Message-ID: <8a9af872-3fb7-a438-a36a-8db6fb660afe@cn.fujitsu.com> (raw)
In-Reply-To: <20190912103535.GB9062@linux.ibm.com>
On 9/12/19 6:35 PM, Mike Rapoport wrote:
> On Thu, Sep 12, 2019 at 10:54:09AM +0800, Cao jin wrote:
>> On 9/11/19 10:42 PM, Mike Rapoport wrote:
>>
>> Sure. BTW, do you want convert all the markups too?
>>
>> :c:type:`foo` -> struct foo
>> %FOO -> FOO
>> ``foo`` -> foo
>> **foo** -> foo
>
> The documentation toolchain can recognize now foo() as a function and does
> not require the :c:func: prefix for that. AFAIK it only works for
> functions, so please don't change the rest of the markup.
>
I see. Thanks for the info. Patch on the way.
--
Sincerely,
Cao jin
prev parent reply other threads:[~2019-09-12 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 3:08 Cao jin
2019-09-11 14:42 ` Mike Rapoport
2019-09-12 2:54 ` Cao jin
2019-09-12 10:35 ` Mike Rapoport
2019-09-12 12:29 ` Cao jin [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=8a9af872-3fb7-a438-a36a-8db6fb660afe@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.ibm.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