From: Roland Dreier <rdreier@cisco.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, openib-general@openib.org
Subject: Re: [PATCH RESEND] net: Move destructor from neigh->ops to neigh_params
Date: Wed, 01 Feb 2006 17:33:39 -0800 [thread overview]
Message-ID: <ada7j8e1r4c.fsf@cisco.com> (raw)
In-Reply-To: <20060201.173137.10844554.davem@davemloft.net> (David S. Miller's message of "Wed, 01 Feb 2006 17:31:37 -0800 (PST)")
David> It's sitting in my backlog, and will be a net-2.6.17 issue
David> not a net-2.6.16 one as we're in bug fix mode there.
David> Sorry if you need this in 2.6.16, but that's not really
David> practical.
No, that's fine... I was just resending in case you were using RED to
manage your backlog. This is a real issue but I don't think it's
hitting a lot of people.
- R.
next prev parent reply other threads:[~2006-02-02 1:33 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 [this message]
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 ` [PATCH] " Andrew Morton
2006-03-07 5:40 ` 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=ada7j8e1r4c.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.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).