From: Ali Bahar <ali@internetdog.org>
To: Kalle Valo <kvalo@adurom.com>
Cc: ali@internetdog.org, Larry Finger <Larry.Finger@lwfinger.net>,
Greg Kroah-Hartman <gregkh@suse.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: r8712u: Most return-values changed from -1 to proper errno macros.
Date: Sat, 16 Jul 2011 18:50:19 +0800 [thread overview]
Message-ID: <20110716105019.GA2176@internetdog.org> (raw)
In-Reply-To: <87zkkevash.fsf@purkki.adurom.net>
Hi Kalle,
On Sat, Jul 16, 2011 at 12:23:42PM +0300, Kalle Valo wrote:
> Ali Bahar <ali@internetdog.org> writes:
>
> > I am aware of the current state of the Linux code's documentation.
> > Habitually, I comment the big-picture as I go along. Industry
> > practice wrt comments differs from Linux's, of course. The comments
> > were in the function heads, not in the bodies, as per
> > Documentation/CodingStyle. The big-picture of the functions is clear
> > once you are familiar enough to begin to modify the code. However,
> > and especially for linux, code is read a thousand times for every
> > time it is written. Most eyeballs could do with a line or two of
> > explanation. To me, Documentation/kernel-docs.txt echoed the need
> > for a big-picture view.
>
> The problem with comments is that they quickly get out of date
Oh boy! I did say I don't want to start a debate, but only to explain
my original intentions. Never the less, I thank you for your response.
It suffices to say that we are mostly in agreement. Key is that my
statements were _not_ about in-body documentation.
> the actual code. So there needs to be a trade-off and in Linux it has
> been that code should be of good quality so that it's easy to read for
> everyone but there will be less comments.
My stance is that, if I were to ever argue otherwise, I should first
dig thru lkml archives for past discussions -- which is only one of
the reason why I don't debate this. :-)
> Kalle Valo
thanks,
ali
next prev parent reply other threads:[~2011-07-16 10:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:47 [PATCH 00/12] rtlwifi: rtl8192se: Merge new driver Larry Finger
2011-05-03 15:01 ` Borislav Petkov
2011-05-03 20:03 ` Larry Finger
2011-05-04 17:01 ` Borislav Petkov
2011-05-04 17:20 ` Larry Finger
2011-05-04 18:06 ` Borislav Petkov
2011-05-04 19:15 ` Larry Finger
2011-05-03 15:59 ` Walter Goldens
2011-05-03 16:45 ` Larry Finger
2011-05-03 20:19 ` Gábor Stefanik
2011-05-03 20:33 ` Larry Finger
2011-05-03 20:38 ` Gábor Stefanik
2011-05-03 20:56 ` Larry Finger
2011-05-03 21:09 ` Gábor Stefanik
2011-05-03 21:35 ` Larry Finger
2011-06-21 12:49 ` r8712u driver for the rtl8192su chip Ali Bahar
2011-06-21 22:08 ` Larry Finger
2011-06-22 1:00 ` Ali Bahar
2011-06-22 2:03 ` Julian Calaby
2011-06-22 2:12 ` Gábor Stefanik
2011-06-22 2:46 ` Ali Bahar
2011-06-22 2:39 ` Ali Bahar
2011-06-22 2:34 ` Larry Finger
2011-06-22 2:56 ` Ali Bahar
2011-06-22 3:09 ` Larry Finger
2011-06-22 3:17 ` Ali Bahar
2011-06-27 7:23 ` Ali Bahar
2011-07-02 17:09 ` Larry Finger
2011-07-03 1:06 ` Ali Bahar
2011-07-03 1:24 ` Larry Finger
2011-07-03 1:47 ` Ali Bahar
2011-07-15 17:11 ` [PATCH 0/2] staging: r8712u: Most return-values changed from -1 to Ali Bahar
2011-07-15 17:11 ` [PATCH 1/2] staging: r8712u: Most return-values changed from -1 to proper errno macros Ali Bahar
2011-07-15 21:00 ` Larry Finger
2011-07-16 3:21 ` Ali Bahar
2011-07-16 9:23 ` Kalle Valo
2011-07-16 10:50 ` Ali Bahar [this message]
2011-07-16 11:44 ` Kalle Valo
2011-07-16 11:55 ` Ali Bahar
2011-07-15 17:11 ` [PATCH 2/2] staging: r8712u: checkpatch errors: trailing whitespace on 2 lines Ali Bahar
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=20110716105019.GA2176@internetdog.org \
--to=ali@internetdog.org \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@suse.de \
--cc=kvalo@adurom.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).