All of lore.kernel.org
 help / color / mirror / Atom feed
From: Massimo Maggi <me@massimo-maggi.eu>
To: grub-devel@gnu.org
Cc: dajhorn@vanadac.com, christopher.siden@delphix.com,
	skiselkov.ml@gmail.com, ryao@cs.stonybrook.edu
Subject: Re: [PATCH 0/5] ZFS Feature flags and LZ4 compression support
Date: Wed, 10 Apr 2013 14:35:23 +0200	[thread overview]
Message-ID: <51655C8B.90603@massimo-maggi.eu> (raw)
In-Reply-To: <510F9696.4040608@massimo-maggi.eu>

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

On 04/02/2013 12:08, Massimo Maggi wrote:
> Massimo Maggi (5):
>   Fix reporting of RAIDZ vdevs in zfsinfo
>   Accept pool version 5000 for feature flags
>   Refactoring of function nvlist_find_value
>   Check for feature flags needed to read from the pool.
>   LZ4 compression in ZFS

Dear Sirs,
I'm writing here to ask public clarifications from the licensing point
of view about the code that I've ported from Grub1 in IllumOS to Grub2.
The original code is contained in those two commits:
https://hg.openindiana.org/upstream/illumos/illumos-gate/rev/2889e2596bd6 [Patch
2/5; 3/5; 4/5]
https://github.com/illumos/illumos-gate/commit/a6f561b4aee75d0d028e7b36b151c8ed8a86bc76
[Patch 5/5].
Respectively authored by Christopher Siden and Sašo Kiselkov.
The code in the patch 1/5 "Fix reporting of RAIDZ vdevs in zfsinfo" is
originally written by me.
I've used only code under the path " usr/src/grub/grub-0.97/".
Those files include the license header "This program is free software;
you can redistribute it and/or modifyit under the terms of the GNU
General Public License as published bythe Free Software Foundation;
either version 2 of the License, or(at your option) any later version."
or include the BSD 2-clause license
(usr/src/grub/grub-0.97/stage2/zfs_lz4.c).
This fact made me assume that there are no licensing problems, however
to ease the merging procedure, a public statement (on the grub-devel
mailing list, as requested from the mantainer) from the original authors
of the code about the legality of this porting would be greatly appreciated.
Regards,
Massimo Maggi


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

  reply	other threads:[~2013-04-10 12:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 11:08 [PATCH 0/5] ZFS Feature flags and LZ4 compression support Massimo Maggi
2013-04-10 12:35 ` Massimo Maggi [this message]
2013-04-10 12:48   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-10 13:06     ` Sašo Kiselkov

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=51655C8B.90603@massimo-maggi.eu \
    --to=me@massimo-maggi.eu \
    --cc=christopher.siden@delphix.com \
    --cc=dajhorn@vanadac.com \
    --cc=grub-devel@gnu.org \
    --cc=ryao@cs.stonybrook.edu \
    --cc=skiselkov.ml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.