From: Andrew Morton <akpm@osdl.org>
To: Rocky Craig <rocky.craig@hp.com>
Cc: minyard@acm.org, Linux Kernel <linux-kernel@vger.kernel.org>,
OpenIPMI Developers <openipmi-developer@lists.sourceforge.net>
Subject: Re: [PATCH 11/12] IPMI: Fix BT long busy
Date: Fri, 8 Dec 2006 12:29:21 -0800 [thread overview]
Message-ID: <20061208122921.5c30d543.akpm@osdl.org> (raw)
In-Reply-To: <457962BF.5050202@hp.com>
On Fri, 08 Dec 2006 06:03:59 -0700
Rocky Craig <rocky.craig@hp.com> wrote:
> Andrew Morton wrote:
>
> >In fact, please don't write macros.
> >
> >
> I see them all over the place (i.e., EXPORT_SYMBOL) so the request
> is a little confusing to me...
It's a general principle. Sometimes they're unavoidable. Other times they
are avoidable but people add them anyway.
> > Please don't write macros which require that the caller have a particular
> >
> >local variable of a particular name.
> >
> >
> I could understand that, even if some people did agree with my desire
> to increase legibility by decreasing visual clutter. I think it also
> provides
> some protection against typos in argument lists.
>
> I'm (naively) curious as to why it's being flagged now as opposed to
> two years ago when I submitted the original additions.
It probably didn't get noticed. Some of the stuff we have in there is
unbelieveable.
> Have reviewers or review methods changed?
>
> Have standards changed?
We have become more vigilant over time.
> Did it just slip under someone's radar two years ago?
I'd say so, yes.
prev parent reply other threads:[~2006-12-08 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 4:39 Corey Minyard
2006-12-03 21:26 ` Andrew Morton
2006-12-04 4:10 ` [Openipmi-developer] " Bela Lubkin
2006-12-08 13:03 ` Rocky Craig
2006-12-08 20:29 ` Andrew Morton [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=20061208122921.5c30d543.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=rocky.craig@hp.com \
/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®