public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: cy_huang <u0084500@gmail.com>,
	robh+dt@kernel.org, cy_huang@richtek.com, will_lin@richtek.com,
	th_chuang@richtek.com, devicetree@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] Add Richtek RT1719 USBPD controller support
Date: Wed, 9 Feb 2022 16:56:46 +0200	[thread overview]
Message-ID: <YgPWLselefw3nGb8@kuha.fi.intel.com> (raw)
In-Reply-To: <YgPQgtcO22W3vZDw@kuha.fi.intel.com>

On Wed, Feb 09, 2022 at 04:32:38PM +0200, Heikki Krogerus wrote:
> On Wed, Feb 09, 2022 at 03:25:19PM +0100, Greg KH wrote:
> > On Wed, Feb 09, 2022 at 10:02:33PM +0800, cy_huang wrote:
> > > 3. Change MODULE_LICENSE from 'GPL v2' to 'GPL'.
> > 
> > Why?  Either is fine, any specific reason you changed this?
> 
> Because I proposed it. I believe everything scripts/checkpatch.pl
> tells me.

It looks like the preference on "GPL" is pretty resent. Check commit
bf7fbeeae6db ("module: Cure the MODULE_LICENSE "GPL" vs. "GPL v2"
bogosity").

thanks,

-- 
heikki

  parent reply	other threads:[~2022-02-09 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 14:02 [PATCH v4 0/2] Add Richtek RT1719 USBPD controller support cy_huang
2022-02-09 14:02 ` [PATCH v4 1/2] dt-bindings: usb: rt1719: Add binding for Richtek RT1719 cy_huang
2022-02-09 14:02 ` [PATCH v4 2/2] usb: typec: rt1719: Add support " cy_huang
2022-02-09 14:59   ` Heikki Krogerus
2022-02-09 14:25 ` [PATCH v4 0/2] Add Richtek RT1719 USBPD controller support Greg KH
2022-02-09 14:32   ` Heikki Krogerus
2022-02-09 14:54     ` Greg KH
2022-02-09 14:56     ` Heikki Krogerus [this message]
2022-02-09 15:07       ` ChiYuan Huang

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=YgPWLselefw3nGb8@kuha.fi.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=th_chuang@richtek.com \
    --cc=u0084500@gmail.com \
    --cc=will_lin@richtek.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