From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Liu, Yujie" <yujie.liu@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [gustavoars:testing/fam01-next20230817] BUILD SUCCESS WITH WARNING dbd3e479335bc8b09ea540102109ac38b0a73336
Date: Sun, 10 Sep 2023 13:43:08 -0600 [thread overview]
Message-ID: <f830b4b0-3d5f-cde8-65d7-e3bee8a40d96@embeddedor.com> (raw)
In-Reply-To: <ZOqykd6tVGip+Swy@rli9-mobl>
On 8/26/23 20:18, Philip Li wrote:
> On Mon, Aug 21, 2023 at 11:26:17AM -0600, Gustavo A. R. Silva wrote:
>> Hi there!
>>
>> It'd be great to add to these reports the versions of the compilers you are using
>> to build the kernel.
>>
>> It's not uncommon that some compiler versions contain bugs. And in cases where kernel
>> developers are aware of those issues, knowing the exact version used to build the
>> kernel will help us determine whether the issues reported may be false positives or
>> not.
>>
>> Maybe just one line at the beginning mentioning the versions:
>>
>> `GCC 13.2.0 and Clang 16.0.0 builds`
>
> Thanks Gustavo for the input, we will add detail version of compiler in the
> summary report.
>
> We will start with the line you suggested, and later will look for a way
> to add it to the warning line since multiple gcc/clang could be involved
> in one round test.
Thank you! :)
--
Gustavo
prev parent reply other threads:[~2023-09-10 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 7:55 [gustavoars:testing/fam01-next20230817] BUILD SUCCESS WITH WARNING dbd3e479335bc8b09ea540102109ac38b0a73336 kernel test robot
2023-08-21 17:26 ` Gustavo A. R. Silva
2023-08-27 2:18 ` Philip Li
2023-09-10 19:43 ` Gustavo A. R. Silva [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=f830b4b0-3d5f-cde8-65d7-e3bee8a40d96@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--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