From: Felipe Balbi <balbi@ti.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: lkml <linux-kernel@vger.kernel.org>, Hemanth V <hemanthv@ti.com>,
Samuel Ortiz <sameo@linux.intel.com>,
akpm <akpm@linux-foundation.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] mfd: twl6030-pwm.c needs MODULE_LICENSE
Date: Sat, 23 Jul 2011 03:33:19 +0300 [thread overview]
Message-ID: <20110723003318.GA13774@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20110722171708.370b2cf5.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 958 bytes --]
Hi,
(adding linux-omap to the loop)
On Fri, Jul 22, 2011 at 05:17:08PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
>
> twl6030_pwm: module license 'unspecified' taints kernel.
>
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: Hemanth V <hemanthv@ti.com>
FWIW:
Acked-by: Felipe Balbi <balbi@ti.com>
> ---
> drivers/mfd/twl6030-pwm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- lnx-30-rc7.orig/drivers/mfd/twl6030-pwm.c
> +++ lnx-30-rc7/drivers/mfd/twl6030-pwm.c
> @@ -161,3 +161,5 @@ void pwm_free(struct pwm_device *pwm)
> kfree(pwm);
> }
> EXPORT_SYMBOL(pwm_free);
> +
> +MODULE_LICENSE("GPL");
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-07-23 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-23 0:17 [PATCH] mfd: twl6030-pwm.c needs MODULE_LICENSE Randy Dunlap
2011-07-23 0:33 ` Felipe Balbi [this message]
2011-07-26 8:31 ` Hemanth V
2011-07-27 9:53 ` Samuel Ortiz
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=20110723003318.GA13774@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=akpm@linux-foundation.org \
--cc=hemanthv@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.