From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>, newlib@sourceware.org
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: Re: [PATCH v3 1/2] aarch64: Sync with ARM-software/optimized-routines
Date: Thu, 5 Oct 2023 14:23:06 +0200 [thread overview]
Message-ID: <4f64c83f-64a9-412e-adeb-933ec8b4eac1@embedded-brains.de> (raw)
In-Reply-To: <eca2ad5d-d833-235c-cad2-a1cd76dab88d@foss.arm.com>
Hello Richard,
On 05.10.23 12:37, Richard Earnshaw wrote:
> This is basically ok, but you're removing an existing license and adding
> a new one from Arm; I think you need to copy the new license into
> COPYING.NEWLIB - it's not enough just to have an SPDX identifier, the
> text of the license must be added somewhere as well.
thanks for the review. I sent v4 of the patch set which should fix the
license issue.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2023-10-05 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 10:05 [PATCH 0/2] " Sebastian Huber
2023-09-12 10:05 ` [PATCH v3 1/2] " Sebastian Huber
2023-10-05 10:37 ` Richard Earnshaw
2023-10-05 12:23 ` Sebastian Huber [this message]
2023-09-12 10:05 ` [PATCH v3 2/2] aarch64: Import memrchr.S Sebastian Huber
2023-09-18 12:25 ` [PATCH 0/2] aarch64: Sync with ARM-software/optimized-routines Sebastian Huber
2023-09-27 9:53 ` Sebastian Huber
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=4f64c83f-64a9-412e-adeb-933ec8b4eac1@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=newlib@sourceware.org \
--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).