From: Christoph Hellwig <hch@infradead.org>
To: Zong Li <zongbox@gmail.com>
Cc: palmer@sifive.com, aou@eecs.berkeley.edu, hch@infradead.org,
zong@andestech.com, vincentc@andestech.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] lib: Add umoddi3 and udivmoddi4 of GCC library routines
Date: Wed, 26 Sep 2018 07:11:59 -0700 [thread overview]
Message-ID: <20180926141159.GA28142@infradead.org> (raw)
In-Reply-To: <7a24493868f29559a1628eed44af15dc10a9940a.1537949825.git.zongbox@gmail.com>
On Wed, Sep 26, 2018 at 04:31:12PM +0800, Zong Li wrote:
> diff --git a/lib/udivmoddi4.c b/lib/udivmoddi4.c
> new file mode 100644
> index 0000000..6518b3a
> --- /dev/null
> +++ b/lib/udivmoddi4.c
> @@ -0,0 +1,309 @@
needs and SPDX tag.
> +/*
> + * This program is free software; you can redistribute it and/or modify it under
> + * the terms of the GNU General Public License as published by the Free
> + * Software Foundation; either version 3, or (at your option) any later
> + * version.
We can't take GPLv3 code for the kernel.
> + * Under Section 7 of GPL version 3, you are granted additional
> + * permissions described in the GCC Runtime Library Exception, version
> + * 3.1, as published by the Free Software Foundation.
> + *
> + * You should have received a copy of the GNU General Public License and
> + * a copy of the GCC Runtime Library Exception along with this program;
> + * see the files COPYING3 and COPYING.RUNTIME respectively.
unless this exception somehow counts (which I doubt), but for that we'd
actually need it in the tree.
next prev parent reply other threads:[~2018-09-26 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 8:31 [PATCH v2 0/5] Fix some bugs on RV32 build fail and issue Zong Li
2018-09-26 8:31 ` [PATCH v2 1/5] RISC-V: Build tishift only on 64-bit Zong Li
2018-09-26 8:31 ` [PATCH v2 2/5] RISC-V: Use swiotlb on RV64 only Zong Li
2018-09-26 8:31 ` [PATCH v2 3/5] lib: Add umoddi3 and udivmoddi4 of GCC library routines Zong Li
2018-09-26 14:11 ` Christoph Hellwig [this message]
2018-09-26 8:31 ` [PATCH v2 4/5] RISC-V: Select GENERIC_LIB_UMODDI3 on RV32 Zong Li
2018-09-26 8:31 ` [PATCH v2 5/5] RISC-V: Avoid corrupting the upper 32-bit of phys_addr_t in ioremap Zong Li
2018-09-28 23:52 ` [PATCH v2 0/5] Fix some bugs on RV32 build fail and issue Palmer Dabbelt
2018-09-29 3:40 ` Zong Li
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=20180926141159.GA28142@infradead.org \
--to=hch@infradead.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=vincentc@andestech.com \
--cc=zong@andestech.com \
--cc=zongbox@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