Linux Documentation
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Bill Wendling <morbo@google.com>
Cc: ndesaulniers@google.com, masahiroy@kernel.org, corbet@lwn.net,
	arnd@arndb.de, keescook@chromium.org, trix@redhat.com,
	nicolas@fjasle.eu, llvm@lists.linux.dev, patches@lists.linux.dev,
	linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/llvm: Add a note about prebuilt kernel.org toolchains
Date: Wed, 5 Apr 2023 13:51:26 -0700	[thread overview]
Message-ID: <20230405205126.GA3280774@dev-arch.thelio-3990X> (raw)
In-Reply-To: <CAGG=3QX65iJEtvMiSD2Ju18f0KfHsi2zPXAQDSh0ScqbCLv=Cg@mail.gmail.com>

On Wed, Apr 05, 2023 at 01:47:44PM -0700, Bill Wendling wrote:
> On Wed, Apr 5, 2023 at 1:44 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > I recently started uploading prebuilt stable versions of LLVM to
> > kernel.org, which should make building the kernel with LLVM more
> > accessible to maintainers and developers. Link them in the LLVM
> > documentation to make this more visible.
> >
> > Link: https://lore.kernel.org/20230319235619.GA18547@dev-arch.thelio-3990X/
> > Suggested-by: Nick Desaulniers <ndesaulniers@google.com>
> > Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> > ---
> >  Documentation/kbuild/llvm.rst | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/kbuild/llvm.rst b/Documentation/kbuild/llvm.rst
> > index bfb51685073c..3e1f67b05ca6 100644
> > --- a/Documentation/kbuild/llvm.rst
> > +++ b/Documentation/kbuild/llvm.rst
> > @@ -171,6 +171,10 @@ Getting Help
> >  Getting LLVM
> >  -------------
> >
> > +We provide prebuilt stable versions of LLVM on `kernel.org <https://kernel.org/pub/tools/llvm/>`_.
> > +Below are links that may be useful for building LLVM from source or procurring
> 
> s/procurring/procuring/

Leave it to me to forget to use ':set spell' :( sometimes I think that
people would have a hard time guessing I am a native English speaker :^)

> Otherwise:
> 
> Reviewed-by: Bill Wendling <morbo@google.com>

Thanks for the quick review! I will send a v2 once others have had a
chance to chime in (unless the person applying this does not mind fixing
it up at that time).

> -bw
> 
> > +it through a distribution's package manager.
> > +
> >  - https://releases.llvm.org/download.html
> >  - https://github.com/llvm/llvm-project
> >  - https://llvm.org/docs/GettingStarted.html
> >
> > ---
> > base-commit: 7e364e56293bb98cae1b55fd835f5991c4e96e7d
> > change-id: 20230405-korg-llvm-tc-docs-84304e881bc5
> >
> > Best regards,
> > --
> > Nathan Chancellor <nathan@kernel.org>
> >
> >

  reply	other threads:[~2023-04-05 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05 20:44 [PATCH] Documentation/llvm: Add a note about prebuilt kernel.org toolchains Nathan Chancellor
2023-04-05 20:47 ` Bill Wendling
2023-04-05 20:51   ` Nathan Chancellor [this message]
2023-04-07 20:05     ` Nick Desaulniers

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=20230405205126.GA3280774@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=arnd@arndb.de \
    --cc=corbet@lwn.net \
    --cc=keescook@chromium.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=morbo@google.com \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=patches@lists.linux.dev \
    --cc=trix@redhat.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