From: David Miller <davem@davemloft.net>
To: teco@inf-net.nl
Cc: hannes@stressinduktion.org, netdev@vger.kernel.org,
equinox@diac24.net, lorenzo@google.com, dave.taht@gmail.com,
ot@cisco.com
Subject: Re: [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match
Date: Wed, 14 Aug 2013 00:55:06 -0700 (PDT) [thread overview]
Message-ID: <20130814.005506.502334877600106930.davem@davemloft.net> (raw)
In-Reply-To: <AFA62E3B-313C-4ECD-BA28-3543635136EE@inf-net.nl>
From: Teco Boot <teco@inf-net.nl>
Date: Wed, 14 Aug 2013 08:40:46 +0200
> What can I do to make progress? Spam Linus?
Reaching past the maintainer of a subsystem is generally considered
extremely inconsiderate and rude.
I would suggest not doing something like that if you have any interest
whatsoever in working peacefully with me in the future.
It sounds like you don't want to use logical arguments to convince me
that this patch meets -stable criteria, and instead you would like to
simply force the issue.
next prev parent reply other threads:[~2013-08-14 7:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 0:34 [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match Hannes Frederic Sowa
2013-08-07 19:58 ` Teco Boot
2013-08-07 20:06 ` Hannes Frederic Sowa
2013-08-09 14:12 ` Teco Boot
2013-08-09 14:19 ` Hannes Frederic Sowa
2013-08-09 14:40 ` Teco Boot
2013-08-09 14:57 ` Hannes Frederic Sowa
2013-08-10 11:39 ` Teco Boot
2013-08-10 12:03 ` Hannes Frederic Sowa
2013-08-13 8:02 ` Teco Boot
2013-08-13 8:15 ` David Miller
2013-08-14 6:40 ` Teco Boot
2013-08-14 7:55 ` David Miller [this message]
2013-08-14 7:59 ` Teco Boot
2013-08-14 8:06 ` Teco Boot
2013-08-14 10:06 ` Hannes Frederic Sowa
2013-08-10 12:15 ` Hannes Frederic Sowa
2015-12-02 9:55 ` [PATCH net 1/1] via-rhine: fix VLAN receive handling regression Teco Boot
2015-12-03 20:11 ` David Miller
2013-08-08 0:17 ` [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match David Miller
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=20130814.005506.502334877600106930.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dave.taht@gmail.com \
--cc=equinox@diac24.net \
--cc=hannes@stressinduktion.org \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=ot@cisco.com \
--cc=teco@inf-net.nl \
/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