From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: kamala@aristanetworks.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ipv6: ip6_pkt_prohibit(_out) should not depend on CONFIG_IPV6_MULTIPLE_TABLES
Date: Sat, 30 Nov 2013 12:51:10 -0500 (EST) [thread overview]
Message-ID: <20131130.125110.248139896351909341.davem@davemloft.net> (raw)
In-Reply-To: <20131130174635.GK24171@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Sat, 30 Nov 2013 18:46:35 +0100
> On Fri, Nov 29, 2013 at 04:39:30PM -0500, David Miller wrote:
>> From: Hannes Frederic Sowa <hannes@stressinduktion.org>
>> Date: Thu, 28 Nov 2013 20:04:11 +0100
>>
>> > Since patch "IPv6: Fixed support for blackhole and prohibit routes" we
>> > need ip6_pkt_prohibit(_out) available without CONFIG_IPV6_MULTIPLE_TABLES
>> > defined.
>> >
>> > Cc: Kamala R <kamala@aristanetworks.com>
>> > Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
>>
>> Please reference the SHA1 ID of the change as well as it's commit
>> header text, thank you.
>
> This patch is a follow-up patch for the first one in this thread which is not
> committed, yet. Either Kamala can squash them into one or I'll repost it
> later.
I think they need to be combined, otherwise bisection is broken.
next prev parent reply other threads:[~2013-11-30 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 9:12 [Patch v3] IPv6: Fixed support for blackhole and prohibit routes Kamala R
2013-11-28 18:49 ` Hannes Frederic Sowa
2013-11-28 19:04 ` [PATCH] ipv6: ip6_pkt_prohibit(_out) should not depend on CONFIG_IPV6_MULTIPLE_TABLES Hannes Frederic Sowa
2013-11-29 21:39 ` David Miller
2013-11-30 17:46 ` Hannes Frederic Sowa
2013-11-30 17:51 ` David Miller [this message]
2013-11-30 17:59 ` Hannes Frederic Sowa
2013-12-02 14:28 ` Kamala R
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=20131130.125110.248139896351909341.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=kamala@aristanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).