mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aditya Garg <gargaditya08@live.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Lukas Wunner <lukas@wunner.de>,
	Hans de Goede <hdegoede@redhat.com>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Orlando Chamberlain <orlandoch.dev@gmail.com>,
	Kerem Karabay <kekrby@gmail.com>
Subject: Re: [PATCH] efi: libstub: add support for the apple_set_os protocol
Date: Sun, 30 Jun 2024 12:09:43 +0000	[thread overview]
Message-ID: <F0BC4076-C386-43C7-8D83-754E545880E9@live.com> (raw)
In-Reply-To: <CAMj1kXFEQDir_VffzHZ0uBMjRqEReNdBZcEQs7kFhi=ipM+y9Q@mail.gmail.com>


> No. You cannot simply add a signed-off-by on someone else's behalf,
> even if you cc the person.
> 
> Andreas contributed code to GRUB (which is a GPLv3 project), and had
> no involvement whatsoever in creating this patch.
> 
> A signed-off-by is a statement on the part of the contributor (which
> may or may not be the author) that the contribution in question
> complies with the requirements imposed by the project in terms of
> copyright and licensing. Linux is GPLv2 not v3, so this code should at
> least be dual licensed in order to be reused directly.
> 
> I did not look at the GRUB patch, and IANAL, but this code invokes an
> Apple provided protocol (which is proprietary) in a hardcoded way for
> interoperability purposes, and so there is not much to
> copyright/license anyway. I would be fine with having just your
> signoff on this patch, but you could ask Andreas for a GPLv2+3 version
> of his GRUB patch if you are not sure.
> 

Code similar to the patch sent by Andreas uses MIT license

https://github.com/0xbb/apple_set_os.efi


  parent reply	other threads:[~2024-06-30 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30  4:42 Aditya Garg
2024-06-30  8:04 ` Lukas Wunner
2024-06-30  9:13   ` Aditya Garg
2024-06-30 10:02     ` Lukas Wunner
2024-06-30 10:50       ` Aditya Garg
2024-06-30 11:04         ` Orlando Chamberlain
2024-06-30 11:25           ` Aditya Garg
2024-06-30 11:27         ` Aditya Garg
2024-06-30 11:29   ` Ard Biesheuvel
2024-06-30 11:56     ` Aditya Garg
2024-06-30 12:58       ` Ard Biesheuvel
2024-06-30 19:18         ` Aditya Garg
2024-06-30 12:09     ` Aditya Garg [this message]
2024-06-30 10:22 ` Lukas Wunner

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=F0BC4076-C386-43C7-8D83-754E545880E9@live.com \
    --to=gargaditya08@live.com \
    --cc=ardb@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=kekrby@gmail.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=orlandoch.dev@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

all inboxes | Powered by JetHome®