linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Add Apple NLS
Date: Fri, 18 May 2012 06:36:24 +0200	[thread overview]
Message-ID: <4FB5D1C8.7020305@gmail.com> (raw)
In-Reply-To: <20120517154707.c3dc2795.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

> Thanks, this looks useful.

> 

You're welcome. Thank you for putting it in your tree.


> 
> Also, I note that the unicode files have
> 
> 	MODULE_LICENSE("Dual BSD/GPL");
> 
> Where did this come from?  Is this a thing you decided upon or is it
> unicode.org's license requirement?
> 

In this case I've taken the precedental approach rather than looking through
licensing files. Other NLS files have a notice that they are based on unicode.org
table, so I've supposed that the license requirements were already checked for them
and the code was reviewed and tested for a long time, so I've picked another nls_*.c
file and only replaced the actual tables using a simple python script. So actually I
don't hold any copyright on this one. All copyright goes to original nls_*.c and to
Unicode consortium.

-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2012-05-18  4:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-13 13:59 [PATCH] Add Apple NLS Vladimir 'φ-coder/phcoder' Serbinenko
2012-05-17 22:47 ` Andrew Morton
2012-05-18  4:36   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-06-01 19:36     ` Yinghai Lu
2012-06-01 21:57       ` Andrew Morton

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=4FB5D1C8.7020305@gmail.com \
    --to=phcoder@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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).