From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Cc: "alistair@alistair23.me" <alistair@alistair23.me>
Subject: Re: [PATCH 2/2] mesa: remove patch disabling asm
Date: Mon, 14 Dec 2020 04:14:12 +0000 [thread overview]
Message-ID: <5c6996a2dbc28630bed661c6d2fa3c4efb51eaf8.camel@intel.com> (raw)
In-Reply-To: <b5957578-08bd-5926-02e7-9c13559e3f5b@gmail.com>
On Fri, 2020-12-11 at 08:41 -0800, Khem Raj wrote:
>
>
> On 12/10/20 11:36 PM, Anuj Mittal wrote:
> > This was originally added for musl only [1]. Upstream has removed
> > this
> > option but we reverted that change during an upgrade to fix certain
> > musl specific compile time issues [2].
> >
> > I compile tested without this patch on musl-x86 and musl-x86-64 and
> > don't see the warnings anymore. Similar textrel issues were fixed
> > upstream so perhaps those helped [3].
> >
> > [1]
> > https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit?id=68bf128e901e89d5b49a28b15d5083b2bf6b536f
> > [2]
> > https://www.openembedded.org/pipermail/openembedded-core/2019-November/289222.html
> > [3]
> > https://gitlab.freedesktop.org/mesa/mesa/-/commit/45206d7673adb1484cbdb3eadaf82e0849c9cdcf?merge_request_iid=1974
> >
>
> Please try running/booting core-image-sato after this change for a
> musl
> based x86 system as well.
Yeah, I had done that and didn't see any problems.
Thanks,
Anuj
next prev parent reply other threads:[~2020-12-14 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 7:36 [PATCH 1/2] mesa: add more details to elf-tls patch Anuj Mittal
2020-12-11 7:36 ` [PATCH 2/2] mesa: remove patch disabling asm Anuj Mittal
2020-12-11 16:33 ` [OE-core] " Alistair Francis
2020-12-11 16:41 ` Khem Raj
2020-12-14 4:14 ` Anuj Mittal [this message]
2020-12-11 16:34 ` [OE-core] [PATCH 1/2] mesa: add more details to elf-tls patch Alistair Francis
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=5c6996a2dbc28630bed661c6d2fa3c4efb51eaf8.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=alistair@alistair23.me \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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