From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: Use a more standard macro for INET_ADDR_COOKIE
Date: Wed, 14 May 2014 16:48:05 -0400 (EDT) [thread overview]
Message-ID: <20140514.164805.1312198151357839253.davem@davemloft.net> (raw)
In-Reply-To: <1400100249.30384.32.camel@joe-AO725>
From: Joe Perches <joe@perches.com>
Date: Wed, 14 May 2014 13:44:09 -0700
> On Wed, 2014-05-14 at 16:08 -0400, David Miller wrote:
>> From: Joe Perches <joe@perches.com>
>> Date: Tue, 13 May 2014 20:30:07 -0700
>>
>> > Missing a colon on definition use is a bit odd so
>> > change the macro for the 32 bit case to declare an
>> > __attribute__((unused)) and __deprecated variable.
>> >
>> > The __deprecated attribute will cause gcc to emit
>> > an error if the variable is actually used.
>> >
>> > Signed-off-by: Joe Perches <joe@perches.com>
>>
>> This is fine, applied, thanks Joe.
>>
>> Perhaps it would have been nicer to make the macros be initializers,
>> so that it still would look like a proper variable declaration at
>> the use sites:
>>
>> const __addrpair var = INET_ADDR_COOKIE(x, y, z);
>>
>> or something like that.
>
> Maybe so, but there's no way to add an __attribute__
> before the = sign for the 32 bit case like that without
> another #define and it would then always require
> initialization too.
Good point.
prev parent reply other threads:[~2014-05-14 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 3:30 Joe Perches
2014-05-14 20:08 ` David Miller
2014-05-14 20:44 ` Joe Perches
2014-05-14 20:48 ` David Miller [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=20140514.164805.1312198151357839253.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®