From: Jaco Kroon <jaco@kroon.co.za>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] Taking the Min and Max macro job
Date: Fri, 09 Feb 2007 09:56:29 +0000 [thread overview]
Message-ID: <45CC454D.30805@kroon.co.za> (raw)
In-Reply-To: <20070207235145.GZ8991@Ahmed>
[-- Attachment #1.1: Type: text/plain, Size: 1010 bytes --]
Vignesh Babu BM wrote:
> On Fri, 2007-02-09 at 09:55 +0100, Richard Knutsson wrote:
>
>>Vignesh Babu BM wrote:
>>
>>>Just went through the archives....
>>>
>>> I tried to recreate the compile-failure (was some time ago since
>>> it
>>> happened) when using min()/max() in a struct but it happily compiled it
>>> so (thankfully) you are correct, just need to use min()/max(). :)
>>>
>>> Richard Knutsson
>>>
>>>Do you mean to say that you were able to compile when the macros were used inside struct?
>>>Im still not able to get that to happen...
>>>
>>>I tried that change in linux-2.6/fs/lockd/mon.c
>>>
>>>static struct rpc_procinfo nsm_procedures[] = {
>>>[SM_MON] = {
>>> .p_proc = SM_MON,
>>> .p_encode = (kxdrproc_t) xdr_encode_mon,
>>> .p_decode = (kxdrproc_t) xdr_decode_stat_res,
>>> .p_bufsiz = max(SM_mon_sz, SM_monres_sz) << 2,
Will work since both SM_mon_sz and SM_monres_sz are compile-time
constants, not true?
[ ... snip ... ]
Jaco
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3233 bytes --]
[-- Attachment #2: Type: text/plain, Size: 168 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2007-02-09 9:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 23:51 [KJ] Taking the Min and Max macro job Ahmed S. Darwish
2007-02-08 6:16 ` Alexey Dobriyan
2007-02-08 9:34 ` Ahmed S. Darwish
2007-02-08 9:41 ` Mehul Jani
2007-02-08 10:14 ` Mehul Jani
2007-02-08 11:40 ` Ahmed S. Darwish
2007-02-08 12:30 ` Mehul Jani
2007-02-08 12:34 ` Ahmed S. Darwish
2007-02-08 16:53 ` Robert P. J. Day
2007-02-08 18:40 ` Mehul Jani
2007-02-09 5:29 ` Mehul Jani
2007-02-09 6:44 ` Vignesh Babu BM
2007-02-09 7:15 ` Richard Knutsson
2007-02-09 7:56 ` Vignesh Babu BM
2007-02-09 8:19 ` Vignesh Babu BM
2007-02-09 8:55 ` Richard Knutsson
2007-02-09 9:41 ` Vignesh Babu BM
2007-02-09 9:56 ` Jaco Kroon [this message]
2007-02-09 12:17 ` Mehul Jani
2007-02-09 18:01 ` Richard Knutsson
2007-02-09 18:10 ` Richard Knutsson
2007-02-09 19:38 ` Mehul Jani
2007-02-09 22:28 ` Richard Knutsson
2007-02-10 5:49 ` Vignesh Babu BM
2007-02-10 8:24 ` Mehul Jani
2007-02-10 11:26 ` Robert P. J. Day
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=45CC454D.30805@kroon.co.za \
--to=jaco@kroon.co.za \
--cc=kernel-janitors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.