From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Pgowda" <pgowda.cve@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, rwmacleod@gmail.com,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: Re: [OE-core] [PATCH v6] Rust Oe-Selftest implementation
Date: Tue, 2 Aug 2022 11:52:18 +0200 [thread overview]
Message-ID: <20220802115218.5eeb964c@booty> (raw)
In-Reply-To: <CALY4986e=cqifcHUNt0buU5+FtHjLju_29SwLhD14rwFd2zU_g@mail.gmail.com>
Hi Pgowda,
On Tue, 2 Aug 2022 14:37:54 +0530
"Pgowda" <pgowda.cve@gmail.com> wrote:
> Hi Luca,
>
> There were around 270 testcase failing when "has-elf-tls" has been
> enabled while building llvm.
> Hence, we had to remove the option to enable the proper working of these tests.
> The patch has been tested on Ubuntu and also fedora (using docker image).
Thanks for the explanation. Then why not adding an explanatory comment,
as below?
# Disabled because.....
# tspec['has-elf-tls'] = True
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-02 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 3:53 [PATCH v6] Rust Oe-Selftest implementation pgowda.cve
2022-08-02 8:38 ` [OE-core] " Luca Ceresoli
2022-08-02 9:07 ` pgowda cve
2022-08-02 9:52 ` Luca Ceresoli [this message]
2022-08-02 12:22 ` pgowda cve
-- strict thread matches above, loose matches on Subject: below --
2022-05-24 20:56 [OE-core] [PATCH v5] " Luca Ceresoli
2022-05-25 4:32 ` [PATCH v6] " pgowda
2022-05-25 7:57 ` [OE-core] " Luca Ceresoli
[not found] ` <16F24A16BC7F056F.12338@lists.openembedded.org>
2022-05-31 13:05 ` Luca Ceresoli
2022-06-03 13:07 ` pgowda cve
2022-06-06 8:51 ` Richard Purdie
2022-06-29 8:18 ` pgowda cve
2022-06-29 16:19 ` Khem Raj
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=20220802115218.5eeb964c@booty \
--to=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rwmacleod@gmail.com \
--cc=vinay.m.engg@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