From: "David S. Miller" <davem@davemloft.net>
To: Adrian Bunk <bunk@stusta.de>
Cc: marcelo.tosatti@cyclades.com, laforge@gnumonks.org,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
patrick@tykepenguin.com, linux-decnet-user@lists.sourceforge.net
Subject: Re: [patch] 2.4.28-rc3: neigh_for_each must be EXPORT_SYMBOL'ed
Date: Sat, 13 Nov 2004 23:25:14 -0800 [thread overview]
Message-ID: <20041113232514.61bf760e.davem@davemloft.net> (raw)
In-Reply-To: <20041113200735.GD2249@stusta.de>
On Sat, 13 Nov 2004 21:07:35 +0100
Adrian Bunk <bunk@stusta.de> wrote:
> neigh_for_each must be EXPORT_SYMBOL'ed (as it is in 2.6):
Good catch Adrian, I'll apply this and push it to
Marcelo.
Thanks.
prev parent reply other threads:[~2004-11-14 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041112180052.GE23215@logos.cnet>
2004-11-13 20:07 ` [patch] 2.4.28-rc3: neigh_for_each must be EXPORT_SYMBOL'ed Adrian Bunk
2004-11-14 7:25 ` David S. 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=20041113232514.61bf760e.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bunk@stusta.de \
--cc=laforge@gnumonks.org \
--cc=linux-decnet-user@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
--cc=patrick@tykepenguin.com \
/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).