linux-csky.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Guo Ren <guoren@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	linux-csky@vger.kernel.org, Guo Ren <ren_guo@c-sky.com>
Subject: Re: [PATCH] csky: Improve abiv1 mem ops performance with glibc codes
Date: Mon, 1 Jul 2019 16:52:29 +0200	[thread overview]
Message-ID: <CAK8P3a0F5-wtJHbLvEwUXE8EnALMpQb5KeX4FK3S90Ce81oN-Q@mail.gmail.com> (raw)
In-Reply-To: <1561786601-19512-1-git-send-email-guoren@kernel.org>

On Sat, Jun 29, 2019 at 7:36 AM <guoren@kernel.org> wrote:
>
> From: Guo Ren <ren_guo@c-sky.com>
>
> These codes are copied from glibc/string directory, they are the generic
> implementation for string operations. We may further optimize them with
> assembly code in the future.
>
> In fact these code isn't tested enough for kernel, but we've tested them
> on glibc and it seems good. We just trust them :)

Are these files from the architecture independent portion of glibc or
are they csky specific? If they are architecture independent, we might
want to see if they make sense for other architectures as well, and
add them to lib/ rather than arch/csky/lib/

Should the SPDX identifier list the original LGPL-2.1 license instead
of GPL-2.0?

       Arnd

  reply	other threads:[~2019-07-01 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-29  5:36 [PATCH] csky: Improve abiv1 mem ops performance with glibc codes guoren
2019-07-01 14:52 ` Arnd Bergmann [this message]
2019-07-01 15:26   ` Guo Ren
2019-07-01 15:46     ` Arnd Bergmann

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=CAK8P3a0F5-wtJHbLvEwUXE8EnALMpQb5KeX4FK3S90Ce81oN-Q@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=guoren@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ren_guo@c-sky.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 NNTP newsgroup(s).