From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC IA64 Hotplug] [Patch 4/7] hotcpu_ia64.patch
Date: Mon, 26 Apr 2004 22:14:54 +0000 [thread overview]
Message-ID: <16525.35294.807376.193745@napali.hpl.hp.com> (raw)
In-Reply-To: <ORSMSX4041XvpFVjCRG0000016f@orsmsx404.amr.corp.intel.com>
Some general comments on this patch:
- Please keep the #include list alphabetically sorted (at least in
the ia64-specific files). Doing so not only makes it easier to
find the right include, but it also tends to expose implicit &
broken include-dependendencies.
- Please don't mangle whitespace unnecessarily (e.g., don't
add/delete whitespace in code that you don't change otherwise).
- There appear to be testing/workaround-hacks in play_dead(). I
assume you're working on resolving those.
- Don't initialize global variables explicitly with zeros. That
happens automatically (and with older compilers, it will needlessly
inflate the size of the data area).
- I really dislike it when function pointers are invoked without
explicit dereferencing. I know that other Linux kernel developers
disagree, but I'd appreciate it if we could at least try to keep
the ia64-code clean in that way. Please use (*foo)(args) instead
of foo(args). Transparency is one of the nicer features of C,
let's take advantage of that!
Thanks,
--david
next prev parent reply other threads:[~2004-04-26 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-25 6:46 [RFC IA64 Hotplug] [Patch 4/7] hotcpu_ia64.patch Ashok Raj
2004-04-26 22:14 ` David Mosberger [this message]
2004-04-27 15:34 ` Grant Grundler
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=16525.35294.807376.193745@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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