netdev - Re: [PATCH net-next] ipv6: remove duplicate neigh

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101217.101403.71116121.davem@davemloft.net>
Date:	Fri, 17 Dec 2010 10:14:03 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6: remove duplicate neigh_ifdown

From: Stephen Hemminger <shemminger@...tta.com>
Date: Fri, 17 Dec 2010 10:01:01 -0800

> Ok. It followed my last patch that did the rt6_ifdown only
> if not loopback. Since you accepted that, I sent the next one.

I applied it to net-2.6, which is how we handle bug fixes.  The
fix naturally propagates to net-next-2.6 the next tiem I do a merge.

This is why I found it quite strange when you were talking about
net-next-2.6 wrt. that bug fix.  We never apply clear important fixes
to net-next-2.6 first, then backport it to net-2.6

If such a net-2.6 dependency exists on a net-next-2.6 patch, you just
need to let me know about it so I can do the merge before applying it.
That's all.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html