From: Greg KH <gregkh@linuxfoundation.org>
To: Shravan Kumar Ramani <shravankr@nvidia.com>
Cc: James Morse <james.morse@arm.com>, linux-edac@vger.kernel.org
Subject: Re: [PATCH v1 2/2] EDAC/bluefield_edac: Update license and copyright info
Date: Mon, 7 Nov 2022 13:37:56 +0100 [thread overview]
Message-ID: <Y2j8JJZKUrkKk4Ze@kroah.com> (raw)
In-Reply-To: <9d584ef2522e2cdc9aa28d3f952ab98b17d961a2.1667561793.git.shravankr@nvidia.com>
On Mon, Nov 07, 2022 at 04:02:54AM -0500, Shravan Kumar Ramani wrote:
> Signed-off-by: Shravan Kumar Ramani <shravankr@nvidia.com>
For obvious reasons, we can't take patches without any changelog text,
and you know this :(
But a meta-comment. You are changing the license and copyright of a
file, without any info at all as to why this is allowed.
Please get your legal council to sign off on such a change in order to
have this be able to be properly reviewed. Please include the
justification for why the license change is allowed, and why the
copyright change is allowed (hint, they are vastly different things, and
really should be two different patches.)
Without that information, changes like this are not allowed, and you
want that to be the case.
So please work with your lawyers and please cc: me on future license
and copyright changes like this.
thanks,
greg k-h
prev parent reply other threads:[~2022-11-07 12:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 9:02 [PATCH v1 0/2] EDAC: Updates to bluefield_edac Shravan Kumar Ramani
2022-11-07 9:02 ` [PATCH v1 1/2] EDAC/bluefield_edac: Add SMC support Shravan Kumar Ramani
2022-11-07 9:02 ` [PATCH v1 2/2] EDAC/bluefield_edac: Update license and copyright info Shravan Kumar Ramani
2022-11-07 12:37 ` Greg KH [this message]
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=Y2j8JJZKUrkKk4Ze@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=shravankr@nvidia.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