From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] IPv6: Warn users when route/max_entries is reached.
Date: Mon, 08 Nov 2010 13:22:03 -0800 (PST) [thread overview]
Message-ID: <20101108.132203.260081813.davem@davemloft.net> (raw)
In-Reply-To: <4CD86709.5090906@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Mon, 08 Nov 2010 13:09:29 -0800
> On 11/08/2010 11:13 AM, Ben Greear wrote:
>> Signed-off-by: Ben Greear<greearb@candelatech.com>
...
> Please don't apply this. I mis-read this code and that warning
> is useless at best in this place.
Ok.
next prev parent reply other threads:[~2010-11-08 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 19:13 [PATCH 1/2] docs: Add neigh/gc_thresh3 and route/max_size documentation Ben Greear
2010-11-08 19:13 ` [PATCH 2/2] IPv6: Warn users when route/max_entries is reached Ben Greear
2010-11-08 21:09 ` Ben Greear
2010-11-08 21:22 ` David Miller [this message]
2010-11-12 22:04 ` [PATCH 1/2] docs: Add neigh/gc_thresh3 and route/max_size documentation 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=20101108.132203.260081813.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=greearb@candelatech.com \
--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).