From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH 0/2] Bonding device changes for later RTNL_LINK
 interface
Date: Thu, 11 Jun 2009 03:12:37 -0700 (PDT)
Message-ID: <20090611.031237.41641418.davem@davemloft.net>
References: <20090610163955.266850193@vyatta.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: fubar@us.ibm.com, bonding-devel@lists.sourceforge.net,
	netdev@vger.kernel.org
To: shemminger@vyatta.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:40138
	"EHLO sunset.davemloft.net" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1754130AbZFKKMf (ORCPT
	<rfc822;netdev@vger.kernel.org>); Thu, 11 Jun 2009 06:12:35 -0400
In-Reply-To: <20090610163955.266850193@vyatta.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Wed, 10 Jun 2009 09:39:55 -0700

> I am working on a RTNL_LINK interface for bonding. These are
> small internal changes that making doing that easier. Plus they
> make bonding devices more like other usages.

These don't apply cleanly to current net-next-2.6, could you
please respin them?

Thanks!