netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: bunk@stusta.de
Cc: netdev@vger.kernel.org, netfilter-devel@lists.netfilter.org,
	linux-kernel@vger.kernel.org, coreteam@netfilter.org,
	bridge@osdl.org, shemminger@osdl.org
Subject: Re: [2.6 patch] BRIDGE_EBT_ARPREPLY must depend on INET
Date: Tue, 19 Jul 2005 14:00:24 -0700 (PDT)	[thread overview]
Message-ID: <20050719.140024.131914996.davem@davemloft.net> (raw)
In-Reply-To: <20050719135529.GH5031@stusta.de>

From: Adrian Bunk <bunk@stusta.de>
Date: Tue, 19 Jul 2005 15:55:29 +0200

> BRIDGE_EBT_ARPREPLY=y and INET=n results in the following compile error:

Applied, thanks Adrian.

      reply	other threads:[~2005-07-19 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 13:55 [2.6 patch] BRIDGE_EBT_ARPREPLY must depend on INET Adrian Bunk
2005-07-19 21:00 ` 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=20050719.140024.131914996.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bridge@osdl.org \
    --cc=bunk@stusta.de \
    --cc=coreteam@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=shemminger@osdl.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).