From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Miguel Ojeda <ojeda@kernel.org>, Yujie Liu <yujie.liu@intel.com>,
Philip Li <philip.li@intel.com>,
julie.du@intel.com, Nathan Chancellor <nathan@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
llvm@lists.linux.dev,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Documentation/llvm: refresh docs for LLVM=1
Date: Wed, 16 Feb 2022 16:07:45 +0100 [thread overview]
Message-ID: <CANiq72kKRFy6jm6L46Tvx11Jo+zwA8NO7f2Bcb17a5jV7BXUTg@mail.gmail.com> (raw)
In-Reply-To: <20220215204947.1719516-1-ndesaulniers@google.com>
Hi Nick,
Thanks for sending this so quickly, no warnings from a quick test:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
A couple of nits below in case you do a v2.
On Tue, Feb 15, 2022 at 9:49 PM Nick Desaulniers
<ndesaulniers@google.com> wrote:
>
> * Word wrap a few columns over 80 lines.
Top to bottom writing? :P
> +For example: ::
This may be simplified to:
For example::
Similar applies elsewhere where a colon + :: marker is wanted. Not
sure what the preferred style is, since the file uses both.
Cheers,
Miguel
prev parent reply other threads:[~2022-02-16 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 20:49 [PATCH] Documentation/llvm: refresh docs for LLVM=1 Nick Desaulniers
2022-02-15 23:48 ` Nathan Chancellor
2022-02-16 15:07 ` Miguel Ojeda [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=CANiq72kKRFy6jm6L46Tvx11Jo+zwA8NO7f2Bcb17a5jV7BXUTg@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=julie.du@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=philip.li@intel.com \
--cc=yujie.liu@intel.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).