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]

Date:	Wed, 22 Jun 2011 21:14:10 +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 16:26 +0200, Arnd Bergmann wrote:
> On Tuesday 21 June 2011, Valdis.Kletnieks@...edu wrote:
> > On Sun, 19 Jun 2011 13:43:40 +0200, Jonas Bonn said:
> 
> > > diff --git a/arch/openrisc/kernel/module.c b/arch/openrisc/kernel/module.c
> > > new file mode 100644
> > > index 0000000..952b129
> > > --- /dev/null
> > > +++ b/arch/openrisc/kernel/module.c
> > > @@ -0,0 +1,126 @@
> > > +/*
> > > + * OpenRISC module.c
> > 
> > Lose the filenames in the headers - you do this in multiple files.
> 
> Good point.

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

/Jonas


Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)