From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] ipv6: remove duplicate neigh_ifdown Date: Fri, 17 Dec 2010 09:49:16 -0800 (PST) Message-ID: <20101217.094916.193712831.davem@davemloft.net> References: <20101216175152.6767d0a7@nehalam> <20101216194254.0f7c7e7b@nehalam> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: shemminger@vyatta.com Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:36917 "EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754883Ab0LQRst (ORCPT ); Fri, 17 Dec 2010 12:48:49 -0500 In-Reply-To: <20101216194254.0f7c7e7b@nehalam> Sender: netdev-owner@vger.kernel.org List-ID: From: Stephen Hemminger Date: Thu, 16 Dec 2010 19:42:54 -0800 > When device is being set to down, neigh_ifdown was being called > twice. Once from addrconf notifier and once from ndisc notifier. > > Signed-off-by: Stephen Hemminger I'll give you a cookie if you can show me how this patch applies to net-next-2.6 cleanly. :-) It only matches the code in net-2.6 which has changed non-trivially in net-next-2.6 If you worked against net-2.6 and thought "I can't think of anything that could have changed in net-next-2.6 in this area", that's not an appropriate way to operate and submit patches. Please don't be so careless, thanks.