From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>,
Hongbo Zhang <hongbo.zhang@linaro.org>
Cc: marcus.shawcroft@arm.com, szabolcs.nagy@arm.com,
libc-alpha@sourceware.org
Subject: Re: [PATCH] aarch64: add HXT Phecda core memory operation ifuncs
Date: Tue, 12 Jun 2018 10:03:00 -0000 [thread overview]
Message-ID: <1398bad5-2996-d776-3823-0912d5bd7118@gotplt.org> (raw)
In-Reply-To: <93d90087-1822-a211-80a8-9aa2089d7a67@redhat.com>
On 06/12/2018 03:12 PM, Florian Weimer wrote:
> For a company, usually someone who has authorization to negotiate and
> sign contracts has to do this, not individual patch authors.
>
> In this case, I think we can still accept the patch because the number
> of lines changes is small (10 lines), but we'd need it for the next patch.
I am ambivalent about the legal significance since although the number
of lines of the change is small it could be argued as being a
significant feature addition given that it chooses optimal routines for
a specific processor core and implicitly provides information about the
Phecda microarchitecture. As such, it is borderline newsworthy,
speaking of which, maybe it needs a NEWS entry like so:
* Improved string routine performance for the Aarch64 HXT Phecda core.
Siddhesh
next prev parent reply other threads:[~2018-06-12 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 9:46 Hongbo Zhang
2018-06-11 12:34 ` Siddhesh Poyarekar
2018-06-12 5:55 ` Hongbo Zhang
2018-06-12 6:27 ` Siddhesh Poyarekar
2018-06-12 8:46 ` Hongbo Zhang
2018-06-12 9:42 ` Florian Weimer
2018-06-12 9:57 ` Hongbo Zhang
2018-06-12 10:03 ` Siddhesh Poyarekar [this message]
2018-06-12 10:07 ` Siddhesh Poyarekar
2018-06-12 10:17 ` Florian Weimer
2018-06-12 10:28 ` Siddhesh Poyarekar
2018-06-13 7:22 ` Hongbo Zhang
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=1398bad5-2996-d776-3823-0912d5bd7118@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fweimer@redhat.com \
--cc=hongbo.zhang@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=marcus.shawcroft@arm.com \
--cc=szabolcs.nagy@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).