public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Florian Meier <florian.meier@koalo.de>,
	Chris Boot <bootc@bootc.net>,
	Martin Sperl <kernel@martin.sperl.org>,
	Eric Anholt <eric@anholt.net>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Mark Brown <broonie@kernel.org>,
	linux-clk@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] dma: bcm2835: make license text and module license match
Date: Sun, 11 Nov 2018 14:39:59 +0530	[thread overview]
Message-ID: <20181111090959.GX12092@vkoul-mobl> (raw)
In-Reply-To: <1540292769-5905-3-git-send-email-stefan.wahren@i2se.com>

On 23-10-18, 13:06, Stefan Wahren wrote:
> The license text is specifying GPL v2 or later but the MODULE_LICENSE
> is set to GPL v2 which means GNU Public License v2 only. So choose the
> license text as the correct one.

Applied after fixing subsystem name, thanks

-- 
~Vinod

  reply	other threads:[~2018-11-11  9:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 11:06 [PATCH 0/3] Fix MODULE_LICENSE of bcm2835 drivers Stefan Wahren
2018-10-23 11:06 ` [PATCH 1/3] clk: bcm2835: make license text and module license match Stefan Wahren
2018-10-23 18:31   ` Eric Anholt
2018-11-06 17:35   ` Stephen Boyd
2018-10-23 11:06 ` [PATCH 2/3] dma: " Stefan Wahren
2018-11-11  9:09   ` Vinod Koul [this message]
2018-10-23 11:06 ` [PATCH 3/3] spi: " Stefan Wahren
2018-11-14 22:27   ` Applied "spi: bcm2835: make license text and module license match" to the spi tree Mark Brown
2018-11-07 18:50 ` [PATCH 0/3] Fix MODULE_LICENSE of bcm2835 drivers Stefan Wahren
2018-11-09 18:48   ` Florian Kauer
2018-11-10 11:37     ` Stefan Wahren
2018-11-10 11:45 ` kernel

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=20181111090959.GX12092@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=bootc@bootc.net \
    --cc=broonie@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=florian.meier@koalo.de \
    --cc=kernel@martin.sperl.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=stefan.wahren@i2se.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