From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6] drm/rockchip: hdmi: add Innosilicon HDMI support
Date: Tue, 26 Jan 2016 01:45:19 +0100 [thread overview]
Message-ID: <1453769119.17181.37.camel@tiscali.nl> (raw)
In-Reply-To: <1453686430-21470-1-git-send-email-ykk@rock-chips.com>
On ma, 2016-01-25 at 09:47 +0800, Yakir Yang wrote:
> --- a/drivers/gpu/drm/rockchip/Kconfig
> +++ b/drivers/gpu/drm/rockchip/Kconfig
> +config ROCKCHIP_INNO_HDMI
> + tristate "Rockchip specific extensions for Innosilicon HDMI"
> + depends on DRM_ROCKCHIP
> + help
> + This selects support for Rockchip SoC specific extensions
> + for the Innosilicon HDMI driver. If you want to enable
> + HDMI on RK3036 based SoC, you should selet this option.
(Really trivial: start indentation with tabs only, please. And
s/selet/select/.)
> --- /dev/null
> +++ b/drivers/gpu/drm/rockchip/inno_hdmi.c
> + * This software is licensed under the terms of the GNU General
> Public
> + * License version 2, as published by the Free Software Foundation,
> and
> + * may be copied, distributed, and modified under those terms.
This states this file is licensed GPL v2 only.
> +MODULE_LICENSE("GPL");
And, according to include/linux/module.h, this means "GNU Public License
v2 or later".
So I think there's a (subtle) mismatch between the license ident used
for this driver and the comment above.
Thanks,
Paul Bolle
next prev parent reply other threads:[~2016-01-26 0:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 1:43 [PATCH v6 0/1] Introduce Innosilicon HDMI driver on Rockchip platforms Yakir Yang
2016-01-25 1:47 ` [PATCH v6] drm/rockchip: hdmi: add Innosilicon HDMI support Yakir Yang
2016-01-26 0:45 ` Paul Bolle [this message]
2016-01-26 2:28 ` Yakir Yang
2016-01-25 12:47 ` [PATCH v6 0/1] Introduce Innosilicon HDMI driver on Rockchip platforms Heiko Stübner
2016-01-26 2:34 ` Yakir Yang
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=1453769119.17181.37.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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