linux-kernel - Re: [PATCH] sound: fix MODULE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGXu5jLGNQj4LqrePpAV_kVBGFX9AxrFs11Hjzg6qk5K=QFxyw@mail.gmail.com>
Date:	Sat, 23 Jun 2012 10:03:17 -0700
From:	Kees Cook <keescook@...omium.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	Ola Lilja <ola.o.lilja@...ricsson.com>,
	alsa-devel@...a-project.org, Joshua Kroll <joshkroll@...gle.com>
Subject: Re: [PATCH] sound: fix MODULE_LICENSE typos

On Sat, Jun 23, 2012 at 3:51 AM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> On Fri, Jun 22, 2012 at 04:21:49PM -0700, Kees Cook wrote:
>> include/linux/license.h does not recognize "GPLv2", so adjust these
>> declarations to add the needed space before the version.
>
> This patch isn't against current -next which doesn't have this issue,
> I've no idea what you generated against as a version with this has never
> even been in -next.  Please do also use subject lines that resemble
> those used in the rest of the subsystem, having to hand edit commit logs
> is tedious.
>
> It seems more sensible to fix license.h, GPLv2 is a pretty common way of
> writing the license name in the wider community.

Ah-ha, yes, I see there's already fixed in -next. Thanks!

http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=85f243912b99b053ce0624c30609f5d8fd4445d2

-Kees

-- 
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/