Re: [PATCH v8 0/5] firmware: add driver data API

From	"Luis R. Rodriguez" <mcgrof@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH v8 0/5] firmware: add driver data API
Date	2017-06-05 23:40 +0200
Message-ID	<tP7Tb-8dq-5@gated-at.bofh.it> (permalink)
References	<tCBP3-4jy-3@gated-at.bofh.it> <tIVBo-6Cu-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri, May 19, 2017 at 12:10:35PM -0700, Luis R. Rodriguez wrote:
> Greg,
> 
> Even though using copyleft-next was fine by Linus [0], AKASHI had brought that
> he expected to see an "or" clause on the license declarations when using
> copyleft-next. This was the only pending issue from the last v7 series [1]. To
> be safe I re-touched the subject and Alan and Ted brought up sufficient reasons
> for preferring the "or" language [2], as such this series goes with the "or"
> language embraced so that it is even clearer than before that GPLv2 applies
> when using copyleft-next on the Linux kernel.

There were two small typos / enhancements as an outcome form that thread, one
was a small a typo (extra parenthesis) as pointed out by Pavel Machek [0] and
the other to add an extra "when" to as recommended by Aaron Wolf [1] on a email
that only went to the copyleft-next mailing list. I've made the small typo
corrections and will be shortly posting a v9 based on this. I've also dropped
changing the license on firmware_class.c in favor or just using copyleft-next
on new files.

FWIW I had also posted two other new test drivers using this dual license as
its the default license I'll be using for new material on my part, one is a
dedicated sysctl test driver [2], and the other a kmod stress test driver [3].
Andrew has merged the sysctl test driver on his -mm tree.

[0] https://lkml.kernel.org/r/20170525201439.GA20750@amd
[1] https://lists.fedorahosted.org/archives/list/copyleft-next@lists.fedorahosted.org/thread/46GQD3C4L3RLOEVPBYXA4PVPJU5CCFUT/
[2] https://lkml.kernel.org/r/20170525233729.18530-2-mcgrof@kernel.org
[3] https://lkml.kernel.org/r/20170526211228.27764-4-mcgrof@kernel.org

> This series depends on the few other UMH fallback lock changes I had submitted
> earlier this month [3], and those remain without any noted issues. As usual,
> all pending changes for this series are available on my linux-next tree on the
> 20170519-driver-data branch [4], this series was rebased on next-20170519.

These are merged now and visible on linux-next, thanks!

  Luis

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH v8 0/5] firmware: add driver data API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:40 +0200
  [PATCH v9 1/5] firmware: add extensible driver data params "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:40 +0200
  [PATCH v9 0/5] firmware: add driver data API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:40 +0200
    [PATCH v9 4/5] firmware: document the extensible driver data API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:40 +0200
    [PATCH v9 2/5] firmware: add extensible driver data API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:50 +0200
    [PATCH v9 5/5] iwlwifi: convert to use driver data API "Luis R. Rodriguez" <mcgrof@kernel.org> - 2017-06-05 23:50 +0200

csiph-web