From: Jonas Bonn <jonas@southpole.se>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 14/19] OpenRISC: Module support
Date: Wed, 22 Jun 2011 22:05:39 +0200 [thread overview]
Message-ID: <1308773139.20122.5268.camel@localhost> (raw)
In-Reply-To: <201106222158.11381.arnd@arndb.de>
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
next prev parent reply other threads:[~2011-06-22 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308483825-6023-1-git-send-email-jonas@southpole.se>
[not found] ` <1308483825-6023-15-git-send-email-jonas@southpole.se>
[not found] ` <31626.1308686616@turing-police.cc.vt.edu>
2011-06-22 14:26 ` [PATCH 14/19] OpenRISC: Module support Arnd Bergmann
2011-06-22 14:26 ` Arnd Bergmann
2011-06-22 19:08 ` [PATCH 1/1] Add default implementations for moduleloader hooks Jonas Bonn
2011-06-22 19:08 ` Jonas Bonn
2011-06-22 19:14 ` [PATCH 14/19] OpenRISC: Module support Jonas Bonn
2011-06-22 19:58 ` Arnd Bergmann
2011-06-22 20:05 ` Jonas Bonn [this message]
2011-06-22 20:46 ` Arnd Bergmann
2011-06-24 8:52 ` Jonas Bonn
2011-06-24 8:52 ` Jonas Bonn
2011-06-24 10:05 ` Arnd Bergmann
2011-06-24 11:06 ` Rusty Russell
2011-06-24 11:06 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308773139.20122.5268.camel@localhost \
--to=jonas@southpole.se \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox