From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Isapnp warning
Date: Sun, 22 Jun 2003 17:00:05 +0200 [thread overview]
Message-ID: <20030622150005.GG6353@lug-owl.de> (raw)
In-Reply-To: <200306221607.15232.phillips@arcor.de>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Sun, 2003-06-22 16:07:14 +0200, Daniel Phillips <phillips@arcor.de>
wrote in message <200306221607.15232.phillips@arcor.de>:
> Hi Alan,
>
> On Saturday 21 June 2003 14:31, Alan Cox wrote:
> > On Sul, 2003-06-15 at 19:36, Geert Uytterhoeven wrote:
>
> How about:
>
> #define if_pci(tokens...) tokens
>
> int pnp_add_irq_resource(struct pnp_dev *dev, int depnum, struct pnp_irq *data)
> {
> if_pci(int i);
> ...
> }
>
> Admittedly uglier than just having the warning disabled by default.
Even whilest I don't like defining variables where I need them (at an
opening "{" or like in "for (int i, i < x, i++)" as Linus suggested it),
this is quite ugly, too. "if_pci(int i)" looks linke an uglyfied
function call, and even while being ugly, it should basically "work"
like a function call. Here, it doesn't, so I consider this a Bad Thing.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-22 14:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 18:36 [PATCH] Isapnp warning Geert Uytterhoeven
2003-06-21 12:31 ` Alan Cox
2003-06-21 14:59 ` Geert Uytterhoeven
2003-06-21 15:04 ` Sean Neakums
2003-06-21 19:51 ` Andrew Morton
2003-06-21 23:53 ` Linus Torvalds
2003-06-22 0:11 ` Arnaldo Carvalho de Melo
2003-06-22 1:41 ` Chris Wedgwood
2003-06-22 1:43 ` Arnaldo Carvalho de Melo
2003-06-22 2:17 ` Andrew Morton
2003-06-22 2:27 ` Chris Wedgwood
2003-06-22 2:59 ` Andrew Morton
2003-06-22 5:50 ` Herbert Xu
2003-06-22 3:43 ` Martin J. Bligh
2003-06-22 4:24 ` Paul Mackerras
2003-06-22 8:32 ` Geert Uytterhoeven
2003-06-22 13:34 ` Daniel Phillips
2003-06-22 5:39 ` gcc 3.3: largest *and* smallest kernels (was Re: [PATCH] Isapnp warning) Barry K. Nathan
2003-06-22 11:31 ` Alan Cox
2003-06-22 13:22 ` GCC speed (was " Daniel Phillips
2003-06-22 17:32 ` Andrew Morton
2003-06-22 17:56 ` Linus Torvalds
2003-06-22 18:58 ` Henning P. Schmiedehausen
2003-06-22 19:12 ` Sam Ravnborg
2003-06-22 19:13 ` Andrew Morton
2003-06-22 19:32 ` Henning Schmiedehausen
2003-06-22 19:51 ` Adrian Bunk
2003-06-22 19:12 ` Daniel Phillips
2003-06-23 1:05 ` Larry McVoy
2002-01-04 11:32 ` Pavel Machek
2003-07-17 10:18 ` Christoph Hellwig
2003-07-17 10:23 ` Jakub Jelinek
2003-07-17 10:27 ` Christoph Hellwig
2003-06-22 8:49 ` [PATCH] Isapnp warning Russell King
2003-06-22 8:39 ` Jörn Engel
2003-06-22 14:07 ` Daniel Phillips
2003-06-22 15:00 ` Jan-Benedict Glaw [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-29 14:49 Geert Uytterhoeven
2003-06-15 19:10 Geert Uytterhoeven
2003-06-09 10:37 Geert Uytterhoeven
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=20030622150005.GG6353@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@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