From: kernel test robot <lkp@intel.com>
To: WANG Rui <wangrui@loongson.cn>, Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Wedson Almeida Filho <wedsonaf@gmail.com>,
Huacai Chen <chenhuacai@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: oe-kbuild-all@lists.linux.dev,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"WANG Xuerui" <kernel@xen0n.name>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev, linux-doc@vger.kernel.org,
loongson-kernel@lists.loongnix.cn,
"WANG Rui" <wangrui@loongson.cn>
Subject: Re: [PATCH] LoongArch: Enable initial Rust support
Date: Sun, 7 Jan 2024 09:06:33 +0800 [thread overview]
Message-ID: <202401070815.6tdJWFme-lkp@intel.com> (raw)
In-Reply-To: <20240106065941.180796-1-wangrui@loongson.cn>
Hi WANG,
kernel test robot noticed the following build warnings:
[auto build test WARNING on rust/rust-next]
[also build test WARNING on linus/master v6.7-rc8 next-20240105]
[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/WANG-Rui/LoongArch-Enable-initial-Rust-support/20240106-150902
base: https://github.com/Rust-for-Linux/linux rust-next
patch link: https://lore.kernel.org/r/20240106065941.180796-1-wangrui%40loongson.cn
patch subject: [PATCH] LoongArch: Enable initial Rust support
reproduce: (https://download.01.org/0day-ci/archive/20240107/202401070815.6tdJWFme-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202401070815.6tdJWFme-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/rust/arch-support.rst:18: WARNING: Malformed table.
vim +18 Documentation/rust/arch-support.rst
14
15 ============ ================ ==============================================
16 Architecture Level of support Constraints
17 ============ ================ ==============================================
> 18 ``loongarch`` Maintained
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-01-07 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 6:59 [PATCH] LoongArch: Enable initial Rust support WANG Rui
2024-01-07 1:06 ` kernel test robot [this message]
2024-01-07 2:28 ` Huacai Chen
2024-01-07 14:29 ` Miguel Ojeda
2024-01-08 3:21 ` WANG Rui
2024-01-10 11:20 ` Miguel Ojeda
2024-01-11 3:17 ` WANG Rui
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=202401070815.6tdJWFme-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=kernel@xen0n.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wangrui@loongson.cn \
--cc=wedsonaf@gmail.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