linux-kernel - Re: Documentation - How to debug ACPI Problems

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]

Date:	Tue, 14 Aug 2007 13:50:11 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Len Brown <lenb@...nel.org>
Cc:	trenn@...e.de, "Brown, Len" <len.brown@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	Jesper Juhl <jesper.juhl@...il.com>,
	Zhang Rui <rui.zhang@...el.com>,
	Alexey Starikovskiy <aystarik@...il.com>
Subject: Re: Documentation - How to debug ACPI Problems

On Tue, 14 Aug 2007, Len Brown wrote:
> > +Thomas Renninger <trenn@...e.de>, 2007
> > +Copyright (C) 2007 SUSE Linux GmbH
> 
> While it seems to be generally customary to identify the authors of Documentation
> files, it doesn't seem to be customary for them to assert a copyright.
> Is this really necessary?  My concern is that it could discourage contributors
> for user or changing the text in any way they see fit.
> 
> can anybody offer guidance on this?

For docs that specify a friendly license explicitly (GPL, BSD, etc), that
should not be a problem.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
-
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/