From: David Miller <davem@davemloft.net>
To: peter.p.waskiewicz.jr@intel.com
Cc: kaber@trash.net, netdev@vger.kernel.org, shemminger@linux-foundation.org
Subject: Re: [RTNETLINK]: Add nested compat attribute
Date: Mon, 25 Jun 2007 17:15:04 -0700 (PDT) [thread overview]
Message-ID: <20070625.171504.13046835.davem@davemloft.net> (raw)
In-Reply-To: <D5C1322C3E673F459512FB59E0DDC329031B5835@orsmsx414.amr.corp.intel.com>
From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Date: Mon, 25 Jun 2007 16:23:02 -0700
> It looks like the one Patrick resent was the older version that requires
> a typecast. This is the function prototype currently in the kernel:
>
> +extern int rtattr_parse_nested_compat(struct rtattr *tb[], int maxattr,
> + struct rtattr *rta, void **data,
> int len);
>
> This is the newer version:
>
> +extern int __rtattr_parse_nested_compat(struct rtattr *tb[], int
> maxattr,
> + struct rtattr *rta, int len);
> +#define rtattr_parse_nested_compat(tb, max, rta, data, len) \
> +({ data = RTA_PAYLOAD(rta) >= len ? RTA_DATA(rta) : NULL; \
> + __rtattr_parse_nested_compat(tb, max, rta, len); })
> +
>
> I can send the update to what's in 2.6.23 as the first patch of my
> series, or I can write my function calls using the older callback (which
> isn't a problem). Which would you prefer?
Either way is fine with me, just use the interface in the tree
for now and we can fix it up if we add the prototype change.
Meanwhile, Patrick please clear up the situation :-)
next prev parent reply other threads:[~2007-06-26 0:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 16:18 [RTNETLINK]: Add nested compat attribute Patrick McHardy
2007-06-22 17:21 ` Patrick McHardy
2007-06-25 17:14 ` Waskiewicz Jr, Peter P
2007-06-25 20:50 ` David Miller
2007-06-25 21:01 ` Waskiewicz Jr, Peter P
2007-06-25 21:29 ` David Miller
2007-06-25 21:33 ` Waskiewicz Jr, Peter P
2007-06-25 21:34 ` David Miller
2007-06-25 21:08 ` Patrick McHardy
2007-06-25 21:32 ` David Miller
2007-06-25 23:23 ` Waskiewicz Jr, Peter P
2007-06-26 0:15 ` David Miller [this message]
2007-06-26 10:04 ` Patrick McHardy
2007-06-26 10:24 ` David Miller
2007-06-26 9:58 ` Patrick McHardy
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=20070625.171504.13046835.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).