linux-kernel - Re: [PATCH 14/19] OpenRISC: Module support

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: <1308773139.20122.5268.camel@localhost>
Date:	Wed, 22 Jun 2011 22:05:39 +0200
From:	Jonas Bonn <jonas@...thpole.se>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH 14/19] OpenRISC: Module support


On Wed, 2011-06-22 at 21:58 +0200, Arnd Bergmann wrote:
> On Wednesday 22 June 2011 21:14:10 Jonas Bonn wrote:
> > What's an acceptable "comment title"?  Most other arch's seem to put the
> > filename there... I understand this is undesirable, but what can I put
> > there instead?  Is "OpenRISC Linux" acceptable, or is nothing at all
> > preferable?
> > 
> > Just want to be clear about what's allowed before I go changing all of
> > these...
> 
> You don't really need anything in the comment, if you want to put something
> there, I'd recommend a one-line summary of what the file is used for.
> 

No license information, copyright, etc?  Nothing?  Would it be
preferable to delete the comments altogether...?

/Jonas

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