From: Christoph Hellwig <hch@infradead.org>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: Pavel Machek <pavel@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
davej@codemonkey.org.uk,
kernel list <linux-kernel@vger.kernel.org>,
paul.devriendt@amd.com, aj@suse.de
Subject: Re: Cpufreq for opteron
Date: Sat, 23 Aug 2003 18:50:22 +0100 [thread overview]
Message-ID: <20030823185022.A32664@infradead.org> (raw)
In-Reply-To: <20030823095521.B14519@bitwizard.nl>; from R.E.Wolff@BitWizard.nl on Sat, Aug 23, 2003 at 09:55:21AM +0200
On Sat, Aug 23, 2003 at 09:55:21AM +0200, Rogier Wolff wrote:
> Guys, good programming practise would leave this in. If you want,
> you could add a comment that in the current code, this is superfluous.
People tend to have different options on good programming practive.
In the linux kenrel world at least these idiom is usually avoided.
next prev parent reply other threads:[~2003-08-23 17:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-22 13:59 Cpufreq for opteron Pavel Machek
2003-08-22 14:43 ` Dave Jones
2003-08-22 19:55 ` Pavel Machek
2003-08-22 20:05 ` Pavel Machek
2003-08-26 23:02 ` Dominik Brodowski
2003-08-22 14:52 ` Christoph Hellwig
2003-08-22 14:55 ` Dave Jones
2003-08-22 19:54 ` Pavel Machek
2003-08-23 7:55 ` Rogier Wolff
2003-08-23 17:50 ` Christoph Hellwig [this message]
2003-08-22 16:25 Andi Kleen
2003-08-22 20:09 paul.devriendt
2003-08-25 8:46 ` Pavel Machek
2003-08-25 13:30 ` Valdis.Kletnieks
2003-08-24 15:31 paul.devriendt
2003-08-25 9:35 ` Pavel Machek
[not found] <99F2150714F93F448942F9A9F112634C080EF006@txexmtae.amd.com.suse.lists.linux.kernel>
[not found] ` <20030825084616.GC403@elf.ucw.cz.suse.lists.linux.kernel>
2003-08-25 10:56 ` Andi Kleen
2003-08-25 12:53 paul.devriendt
2003-08-25 13:51 ` Pavel Machek
2003-08-25 14:09 paul.devriendt
2003-08-27 0:43 paul.devriendt
2003-08-27 5:13 ` Dominik Brodowski
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=20030823185022.A32664@infradead.org \
--to=hch@infradead.org \
--cc=R.E.Wolff@BitWizard.nl \
--cc=aj@suse.de \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.devriendt@amd.com \
--cc=pavel@suse.cz \
/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).