public inbox for linux-spdx@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Ryder Lee <ryder.lee@kernel.org>,
	Sam Shih <sam.shih@mediatek.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-spdx@vger.kernel.org,
	kernel-janitors <kernel-janitors@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPL-1.0-licensed code for files drivers/clk/mediatek/clk-mt7986* included with commit ec97d23c8e22 ("clk: mediatek: add mt7986 clock support")
Date: Thu, 13 Jan 2022 17:43:45 -0800	[thread overview]
Message-ID: <20220114014346.947F3C36AE3@smtp.kernel.org> (raw)
In-Reply-To: <0f3836a37d36dece52213d4b33e2b666cb187fc2.camel@mediatek.com>

Quoting Sam Shih (2022-01-10 04:12:57)
> Hi Luka/Stephen,
> 
> This is my mistake, I seem to use an old license header on it.
> Just like "clk-mt7986-eth.c" in the same patch series,
> 
> 
> https://lore.kernel.org/all/20211217121148.6753-4-sam.shih@mediatek.com/
> 
> I intend to license "clk-mt7986-apmixed.c", "clk-mt7986-infracfg.c",
> and "clk-mt7986-topckgen" under the kernel's standard GPL-2.0.
> 
> Should I need to resend this patch?
> Or I can just send a follow-up patch to fix it?
> 

Please send a followup to fix it.

      reply	other threads:[~2022-01-14  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  9:56 GPL-1.0-licensed code for files drivers/clk/mediatek/clk-mt7986* included with commit ec97d23c8e22 ("clk: mediatek: add mt7986 clock support") Lukas Bulwahn
2022-01-10 12:12 ` Sam Shih
2022-01-14  1:43   ` Stephen Boyd [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=20220114014346.947F3C36AE3@smtp.kernel.org \
    --to=sboyd@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=ryder.lee@kernel.org \
    --cc=sam.shih@mediatek.com \
    --cc=tglx@linutronix.de \
    /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