From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Nick Terrell <terrelln@fb.com>, kernel test robot <lkp@intel.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-all] Re: lib/zstd/common/debug.h: zstd_deps.h is included more than once.
Date: Tue, 29 Mar 2022 18:18:27 +0800 [thread overview]
Message-ID: <e21b9fff-57c7-b1e3-6928-46d6088a57b3@intel.com> (raw)
In-Reply-To: <6F25888B-F700-4DFD-A60F-7A542D2DFF5F@fb.com>
Hi Nick,
Sorry for the inconvenience, we will add it to ignore list.
Best Regards,
Rong Chen
On 3/29/2022 9:43 AM, Nick Terrell wrote:
>
>
>> On Mar 26, 2022, at 3:26 PM, kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 710f5d627a98e86f821aceb840b8f2f1fcc6cf75
>> commit: e0c1b49f5b674cca7b10549c53b3791d0bbc90a8 lib: zstd: Upgrade to latest upstream zstd version 1.4.10
>> date: 5 months ago
>> compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>>
>> includecheck warnings: (new ones prefixed by >>)
>>>> lib/zstd/common/debug.h: zstd_deps.h is included more than once.
>
> This is intentional, and working as expected.
>
> Best,
> Nick Terrell
>
>> --
>> 0-DAY CI Kernel Test Service
>> https://01.org/lkp
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
>
prev parent reply other threads:[~2022-03-29 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 22:26 kernel test robot
2022-03-29 1:43 ` Nick Terrell
2022-03-29 10:18 ` Chen, Rong A [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=e21b9fff-57c7-b1e3-6928-46d6088a57b3@intel.com \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=terrelln@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
all inboxes | Powered by JetHome®