From: Andrew Morton <akpm@osdl•org>
To: Roland Dreier <rdreier@cisco•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, openib-general@openib•org
Subject: Re: [PATCH] net: Move destructor from neigh->ops to neigh_params
Date: Mon, 6 Mar 2006 21:16:30 -0800 [thread overview]
Message-ID: <20060306211630.0df79464.akpm@osdl.org> (raw)
In-Reply-To: <adazmlmmy7v.fsf@cisco.com>
Roland Dreier <rdreier@cisco•com> wrote:
>
> struct neigh_ops currently has a destructor field, which no in-kernel
> drivers outside of infiniband use.
net/atm/clip.c begs to disagree.
I'm also wondering why a combination of the net and infiniband trees does this:
drivers/infiniband/ulp/ipoib/ipoib_multicast.c: In function `ipoib_mcast_free':
drivers/infiniband/ulp/ipoib/ipoib_multicast.c:118: error: structure has no member named `destructor'
next prev parent reply other threads:[~2006-03-07 5:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-23 21:27 [PATCH] net: Move destructor from neigh->ops to neigh_params Roland Dreier
2006-01-23 21:54 ` David S. Miller
2006-02-02 1:28 ` [PATCH RESEND] " Roland Dreier
2006-02-02 1:31 ` David S. Miller
2006-02-02 1:33 ` Roland Dreier
2006-02-02 1:34 ` YOSHIFUJI Hideaki / 吉藤英明
2006-02-21 3:42 ` Roland Dreier
2006-02-21 4:01 ` David S. Miller
2006-02-21 4:48 ` Roland Dreier
2006-02-21 4:55 ` David S. Miller
2006-03-04 1:58 ` David S. Miller
2006-03-07 5:16 ` Andrew Morton [this message]
2006-03-07 5:40 ` Re: [PATCH] " Shirley Ma
2006-03-07 5:44 ` Roland Dreier
2006-03-07 6:11 ` David S. Miller
2006-03-07 5:50 ` Roland Dreier
2006-03-07 19:21 ` [PATCH] IPoIB: Fix build now that destructor is in neigh_params Roland Dreier
2006-03-07 22:53 ` David S. Miller
2006-03-07 22:56 ` Roland Dreier
2006-03-07 19:22 ` [PATCH] [NET]: Move destructor from neigh->ops to neigh_params Roland Dreier
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=20060306211630.0df79464.akpm@osdl.org \
--to=akpm@osdl$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=openib-general@openib$(echo .)org \
--cc=rdreier@cisco$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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