From: kernel test robot <lkp@intel.com>
To: Nick Desaulniers <ndesaulniers@google.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Nathan Chancellor <nathan@kernel.org>, Tom Rix <trix@redhat.com>,
Nicolas Schier <nicolas@fjasle.eu>,
Jonathan Corbet <corbet@lwn.net>,
llvm@lists.linux.dev, linux-kbuild@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Bill Wendling <morbo@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Yonghong Song <yhs@fb.com>, Daniel Kolesa <q66@chimera-linux.org>,
Chris Mason <chris.mason@fusionio.com>
Subject: Re: [PATCH] Documentation/llvm: add Chimera Linux, Google and Meta datacenters
Date: Thu, 2 Feb 2023 17:32:40 +0800 [thread overview]
Message-ID: <202302021759.syE8waoZ-lkp@intel.com> (raw)
In-Reply-To: <20230201192509.4124319-1-ndesaulniers@google.com>
Hi Nick,
I love your patch! Perhaps something to improve:
[auto build test WARNING on masahiroy-kbuild/for-next]
[also build test WARNING on masahiroy-kbuild/fixes linus/master v6.2-rc6 next-20230202]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nick-Desaulniers/Documentation-llvm-add-Chimera-Linux-Google-and-Meta-datacenters/20230202-032729
base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next
patch link: https://lore.kernel.org/r/20230201192509.4124319-1-ndesaulniers%40google.com
patch subject: [PATCH] Documentation/llvm: add Chimera Linux, Google and Meta datacenters
reproduce:
# https://github.com/intel-lab-lkp/linux/commit/fb73005aa3c6a4052e30f0f0dc2c608bafd8acce
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nick-Desaulniers/Documentation-llvm-add-Chimera-Linux-Google-and-Meta-datacenters/20230202-032729
git checkout fb73005aa3c6a4052e30f0f0dc2c608bafd8acce
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
make htmldocs
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/kbuild/llvm.rst:13: WARNING: Unknown target name: "chromeos https://www.chromium.org/chromium-os>".
vim +13 Documentation/kbuild/llvm.rst
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 12
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 @13 The Linux kernel has always traditionally been compiled with GNU toolchains
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 14 such as GCC and binutils. Ongoing work has allowed for `Clang
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 15 <https://clang.llvm.org/>`_ and `LLVM <https://llvm.org/>`_ utilities to be
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 16 used as viable substitutes. Distributions such as `Android
fcf1b6a35c16ac5 Nick Desaulniers 2020-02-26 17 <https://www.android.com/>`_, `ChromeOS
fb73005aa3c6a40 Nick Desaulniers 2023-02-01 18 https://www.chromium.org/chromium-os>`_, `OpenMandriva
fb73005aa3c6a40 Nick Desaulniers 2023-02-01 19 <https://www.openmandriva.org/>`_, and `Chimera Linux
fb73005aa3c6a40 Nick Desaulniers 2023-02-01 20 <https://chimera-linux.org/>`_ use Clang built kernels. Google's and Meta's
fb73005aa3c6a40 Nick Desaulniers 2023-02-01 21 datacenter fleets also run kernels built with Clang.
fb73005aa3c6a40 Nick Desaulniers 2023-02-01 22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-02-02 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 19:25 Nick Desaulniers
2023-02-01 19:54 ` Tom Rix
2023-02-01 21:16 ` Nathan Chancellor
2023-02-01 23:28 ` Sedat Dilek
2023-02-02 9:32 ` kernel test robot [this message]
2023-02-02 18:05 ` [PATCH v2] " 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=202302021759.syE8waoZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris.mason@fusionio.com \
--cc=corbet@lwn.net \
--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=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=q66@chimera-linux.org \
--cc=trix@redhat.com \
--cc=yhs@fb.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
Powered by JetHome