From: David McCullough <davidm@snapgear.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RANT] Totally inadequate commenting in flat.h
Date: Wed, 6 Nov 2002 10:59:41 +1000 [thread overview]
Message-ID: <20021106105941.A17501@beast.internal.moreton.com.au> (raw)
In-Reply-To: <15816.23157.790358.720568@argo.ozlabs.ibm.com>; from paulus@samba.org on Wed, Nov 06, 2002 at 10:55:33AM +1100
Hi Paul,
Fair comment, however, have you looked at a lot of the other files
in include/linux ? Plenty of examples with the same lack of comments,
a good one that does essentially the same thing as flat.h:
include/linux/elf.h
No excuses though, here's a patch to add a comment about what the file is
used for,
Cheers,
Davidm
Index: include/linux/flat.h
===================================================================
RCS file: include/linux/flat.h,v
retrieving revision 1.2
diff -u -1 -r1.2 flat.h
--- include/linux/flat.h 16 Oct 2002 04:34:28 -0000 1.2
+++ include/linux/flat.h 6 Nov 2002 00:51:25 -0000
@@ -4,2 +4,5 @@
* Copyright (C) 2002 David McCullough <davidm@snapgear.com>
+ *
+ * This file provides the definitions and structures needed to
+ * support uClinux flat-format executables.
*/
Jivin Paul Mackerras lays it down ...
> Looking over the recent changes in Linus' tree, I saw there was this
> new file, include/linux/flat.h. Hmmm, uninformative name, what's this
> file about? I look in the file and here is how it starts:
>
> /* Copyright (C) 1998 Kenneth Albanowski <kjahds@kjahds.com>
> * The Silver Hammer Group, Ltd.
> * Copyright (C) 2002 David McCullough <davidm@snapgear.com>
> */
>
> #ifndef _LINUX_FLAT_H
> #define _LINUX_FLAT_H
>
> #define FLAT_VERSION 0x00000004L
>
> /*
> * To make everything easier to port and manage cross platform
> * development, all fields are in network byte order.
> */
>
> struct flat_hdr {
> char magic[4];
> unsigned long rev; /* version (as above) */
>
> etc.
>
> *Completely* uninformative. How is anyone supposed to know what this
> relates to? Is it something to do with a network device, or a
> filesystem, or an executable format, or what?
>
> [And no, don't reply to this telling me what it's about, add some
> comments to the file instead.]
>
> Paul.
--
David McCullough: Ph: +61 7 3435 2815 http://www.SnapGear.com
davidm@snapgear.com Fx: +61 7 3891 3630 Custom Embedded Solutions + Security
prev parent reply other threads:[~2002-11-06 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 23:55 Paul Mackerras
2002-11-06 0:59 ` David McCullough [this message]
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=20021106105941.A17501@beast.internal.moreton.com.au \
--to=davidm@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®