Hi Chris,
On Fri, Nov 30, 2018 at 5:10 PM Chris Brandt <Chris.Brandt@xxxxxxxxxxx> wrote:
> On Friday, November 30, 2018 1, Geert wrote:
> > > So in our RZ/A BSP that I release to customers I would use this dual
> > > license. You can see the exact same license in a number of dts files in
> > > mainline.
> >
> > Note that your file includes
> >
> > #include <dt-bindings/gpio/gpio.h>
> > #include <dt-bindings/pinctrl/r7s9210-pinctrl.h>
> >
> > both of which are
> >
> > include/dt-bindings/gpio/gpio.h:/* SPDX-License-Identifier: GPL-2.0 */
> > include/dt-bindings/pinctrl/r7s9210-pinctrl.h:/*
> > SPDX-License-Identifier: GPL-2.0 */
>
> After I wrote that, I realized that we'll always have:
> #include "r7s9210.dtsi"
> Which I have as GPL-2.0....so the dual license idea in pointless.
>
> So to make things easy, I'll just drop the dual license thing and just
> use SPDX GPL-2.0
That's one solution.
Another solution would be to relicense all DT binding definitions and DTS files.
Cfr. e.g. commit d061864b89c3234b ("ARM: dt: relicense two DT binding IRQ
headers").
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
