linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: devicetree@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] dt-bindings: arm: Convert RDA Micro board/soc bindings to json-schema
Date: Tue, 9 Jul 2019 13:02:52 -0600	[thread overview]
Message-ID: <CAL_JsqKWML51A330RXarJaZReiPNeFdCsMbsse3hoNE1pKqc2A@mail.gmail.com> (raw)
In-Reply-To: <20190709184459.GA11886@Mani-XPS-13-9360>

On Tue, Jul 9, 2019 at 12:45 PM Manivannan Sadhasivam
<manivannan.sadhasivam@linaro.org> wrote:
>
> On Tue, Jul 09, 2019 at 12:41:19PM -0600, Rob Herring wrote:
> > On Tue, Jul 9, 2019 at 12:29 PM Rob Herring <robh@kernel.org> wrote:
> > >
> > > On Tue, Jul 9, 2019 at 11:15 AM Manivannan Sadhasivam
> > > <manivannan.sadhasivam@linaro.org> wrote:
> > > >
> > > > Hi Rob,
> > > >
> > > > On Tue, Jun 18, 2019 at 03:22:28PM -0600, Rob Herring wrote:
> > > > > Convert RDA Micro SoC bindings to DT schema format using json-schema.
> > > > >
> > > > > Cc: "Andreas Färber" <afaerber@suse.de>
> > > > > Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> > > > > Signed-off-by: Rob Herring <robh@kernel.org>
> > > > > ---
> > > > > Andreas, Update the license on this one too to dual licensed if you
> > > > > want.
> > > >
> > > > I'm fine with GPL-2.0. Since there isn't any other RDA specific patches
> > > > in my tree, you want to take this patch? Else I have to send the Pull
> > > > Request to ARM SoC folks with this patch alone.
> > >
> > > Okay, I can take it. The preference is actually dual licensed which is
> > > why I asked, but that can be done later.
> >
> > And is that an ack from you?
>
> Yes, here is the formal tag:
>
> Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
> Also, Andreas asked to switch to Dual license for Actions platform since he
> is the maintainer of it. But for RDA he is not, so I don't think there will
> be a concern here (I'm fine with GPL-2.0).

It's authorship that matters and Andreas was the author on the
original file. The maintainer only has a say in what license they'll
accept.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-07-09 19:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18 21:22 [PATCH] dt-bindings: arm: Convert RDA Micro board/soc bindings to json-schema Rob Herring
2019-07-09 17:03 ` Rob Herring
2019-07-09 17:15 ` Manivannan Sadhasivam
2019-07-09 18:29   ` Rob Herring
2019-07-09 18:41     ` Rob Herring
2019-07-09 18:44       ` Manivannan Sadhasivam
2019-07-09 19:02         ` Rob Herring [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=CAL_JsqKWML51A330RXarJaZReiPNeFdCsMbsse3hoNE1pKqc2A@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=manivannan.sadhasivam@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).