From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] glibc: Drop fsqrt implementation patches for fsl ppc
Date: Mon, 06 Dec 2021 23:32:09 +0000 [thread overview]
Message-ID: <61881d47fe575c33b194fc099b9688788e33f1d1.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1sqK0Nxp3NBggH7br4K7Qyxx6voMk1rUXJpVhuxBTBSrUQ@mail.gmail.com>
On Mon, 2021-12-06 at 15:28 -0800, Khem Raj wrote:
>
>
> On Mon, Dec 6, 2021 at 2:51 PM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I did test such a patch today as well since we discussed it. I'd propose
> > this
> > commit message since we need to say why:
> >
> > """
> >
> > glibc: Drop ppc sqrt optimisations
> >
> > OpenEmbedded isn't an upstream or a patch repository. These are
> > optimisations
> > which for reasons unknown were never merged into upstream glibc. We have no
> > active ppc maintainers and these patches are at an evolutionary dead end.
> > Since they are optimisations, there may be small performance regressions by
> > removing them but OE can't carry patches like this indefinitely and these
> > appear to have no future.
> > """
> >
>
>
> This sounds good to me. I guess will add it to commit or do you want me to
> send v2. This passed my local testing on qemuppc
>
I can sort if you're ok with it, thanks.
Cheers,
Richard
next prev parent reply other threads:[~2021-12-06 23:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 22:14 [PATCH 1/2] glibc: Drop fsqrt implementation patches for fsl ppc Khem Raj
2021-12-06 22:14 ` [PATCH 2/2] ffmpeg: Fix build on ppc32 Khem Raj
2021-12-06 22:51 ` [OE-core] [PATCH 1/2] glibc: Drop fsqrt implementation patches for fsl ppc Richard Purdie
2021-12-06 23:28 ` Khem Raj
2021-12-06 23:32 ` Richard Purdie [this message]
2021-12-07 2:09 ` 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=61881d47fe575c33b194fc099b9688788e33f1d1.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--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