From: Nathan Scott <nathans@sgi.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-xfs@oss.sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Parenthesize macros in xfs
Date: Tue, 21 Mar 2006 08:46:19 +1100 [thread overview]
Message-ID: <20060321084619.E653275@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0603202239110.11933@yvahk01.tjqt.qr>; from jengelh@linux01.gwdg.de on Mon, Mar 20, 2006 at 10:39:45PM +0100
Hi Jan,
On Mon, Mar 20, 2006 at 10:39:45PM +0100, Jan Engelhardt wrote:
> >> while browsing through the xfs/linux source, I noticed that many macros do
> >> not do proper bracing. I have started to cook up a patch, but would like
> >> feedback first before I continue for nothing.
> >> It goes like this:
> >> ...
> >
> >That looks fine. Please be sure to work on the -mm tree or on
> >CVS on oss.sgi.com, so as to reduce your level of patch conflict.
> >
>
> Hm, would not it even be better to make them 'static inline' functions?
Probably, I guess I'd want to see how invasive the patch becomes...?
I really dislike those _ACL macros (around that example you gave, that
could do with a cleanup all of its own - switching to xfs_acl_ maybe).
Also watch for macros that modify their parameters, I got burned by
doing an inline conversion a few releases back on just such a beast..
cheers.
--
Nathan
next prev parent reply other threads:[~2006-03-20 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 21:09 Jan Engelhardt
2006-03-20 21:23 ` Nathan Scott
2006-03-20 21:39 ` Jan Engelhardt
2006-03-20 21:46 ` Nathan Scott [this message]
2006-03-25 21:35 ` Jan Engelhardt
2006-03-25 22:38 ` Andreas Schwab
2006-03-25 23:23 ` Jan Engelhardt
2006-03-25 23:45 ` Andreas Schwab
2006-03-26 9:26 ` Jan Engelhardt
2006-03-26 12:19 ` Måns Rullgård
2006-03-26 12:30 ` Kyle Moffett
2006-03-26 14:23 ` Andreas Schwab
2006-03-25 23:26 ` Jan Engelhardt
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=20060321084619.E653275@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.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®