[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTimkxi0BofJYv_tRj8Et+OZFu+VfBw@mail.gmail.com>
Date: Mon, 23 May 2011 20:45:14 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Linux Kernel Network Developers <netdev@...r.kernel.org>
Cc: David Miller <davem@...emloft.net>,
Jay Vosburgh <fubar@...ibm.com>,
Andy Gospodarek <andy@...yhouse.net>
Subject: [RFC Patch] bonding: move to net/ directory
Hello, Jay, Andy,
Is there any peculiar reason that bonding code has to stay
in drivers/net/ directory?
Since bonding and bridge are somewhat similar, both of
which are used to "bond" two or more devices into one,
and bridge code is already in net/bridge/, so I think it also
makes sense to move bonding code into net/bonding/ too.
This could also help to grep the source more easily. :)
What do you think about the patch below?
(Note, this patch is against net-next-2.6.)
Thanks!
Signed-off-by: WANG Cong <xiyou.wangcong@...il.com>
Cc: "David Miller" <davem@...emloft.net>
Cc: Jay Vosburgh <fubar@...ibm.com>
Cc: Andy Gospodarek <andy@...yhouse.net>
---
View attachment "net-bonding-movement.diff" of type "text/x-patch" (6476 bytes)
Powered by blists - more mailing lists