From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ryusuke-sG5X7nlA6pw@public.gmane.org,
konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
Subject: [PATCH 0/1] replace crc32.c
Date: Fri, 19 Nov 2010 17:31:06 +0900 [thread overview]
Message-ID: <1290155467-5475-1-git-send-email-jir@unicus.jp> (raw)
Hi,
I think we've had consensus that libnilfs2 should be LGPLed.
The problems are included GPLed kernel header(nilfs2_fs.h) and
crc32.c derived from GPL2 base code.
http://www.mail-archive.com/linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg00489.html
The kernel header is properly re-licensed as LGPL2.1 in 2.6.37 merge window.
Thus the only problem is crc32.c now.
The following patch addresses the remaining problem.
The patch replaces crc32.c implementation.
The implementation is based on the jamlib(*1) and is LGPL2.1.
*1) http://sourceforge.net/projects/jamlib/
I've checked the compatibility on x86, ppc32 and mixed environments.
Everything was OK.
thanks, regards
--
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-11-19 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 8:31 Jiro SEKIBA [this message]
[not found] ` <1290155467-5475-1-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-11-19 8:31 ` [PATCH 1/1] replace crc32.c Jiro SEKIBA
2010-11-19 9:06 ` [PATCH 0/1] " Ryusuke Konishi
2010-11-19 10:23 ` [PATCH 0/2] nilfs-utils: re-license nilfs library Ryusuke Konishi
2010-11-19 10:23 ` [PATCH 1/2] nilfs-utils: change library license to LGPL Ryusuke Konishi
2010-11-19 10:23 ` [PATCH 2/2] nilfs-utils: insert LGPL preamble in COPYING file Ryusuke Konishi
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=1290155467-5475-1-git-send-email-jir@unicus.jp \
--to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
/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).