linux-kernel - Re: [PATCH v6 2/5] ARM: Add Krait L2 register accessor functions

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140408171929.68f328a9@alan.etchedpixels.co.uk>
Date:	Tue, 8 Apr 2014 17:19:29 +0100
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Christopher Covington <cov@...eaurora.org>,
	Stephen Boyd <sboyd@...eaurora.org>,
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-edac@...r.kernel.org,
	Mark Rutland <mark.rutland@....com>,
	Russell King <linux@....linux.org.uk>,
	Courtney Cavin <courtney.cavin@...ymobile.com>
Subject: Re: [PATCH v6 2/5] ARM: Add Krait L2 register accessor functions

On Tue, 8 Apr 2014 17:10:56 +0200
Borislav Petkov <bp@...en8.de> wrote:

> On Tue, Apr 08, 2014 at 10:25:01AM -0400, Christopher Covington wrote:
> > As I understand it, the license authors. They find it important to maintain
> > clarity even when files get copied into other projects.
> > 
> > http://www.gnu.org/licenses/gpl-howto.html
> > 
> > http://www.gnu.org/licenses/gpl-faq.html#NoticeInSourceFile
> 
> Right, so what is wrong with stating the same thing in two lines:
> 
> "Copyright (c) 2011-2013, The Linux Foundation. All rights reserved.
> 
> This file is licensed under GNU GPLv2. See COPYING for full license text.

The COPYING file may not be present. There may be cases where the absence
of the warranty statement in the header is problematic etc etc.

Corporate legals have their own policies on this and there is no point
fighting them because

- they are the ones qualified to make the decision

- the corporate legal angle is often "do this or don't release it"

- we have huge numbers of files using that same no warranty in every
  file, and major companies who specify it must be present in their code
  releases


Including the without warranty is standard practice at a lot of
companies. It's not even wasting space - it'll compress beautifully as
there are already lots of similar headers all over the tree.

Alan
--
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/