From: David Miller <davem@davemloft.net>
To: andy@greyhouse.net
Cc: amwang@redhat.com, linux-kernel@vger.kernel.org,
fubar@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [V2 Patch] bonding: move procfs code into bond_procfs.c
Date: Wed, 09 Mar 2011 13:34:39 -0800 (PST) [thread overview]
Message-ID: <20110309.133439.246540302.davem@davemloft.net> (raw)
In-Reply-To: <20110307161740.GT11864@gospo.rdu.redhat.com>
From: Andy Gospodarek <andy@greyhouse.net>
Date: Mon, 7 Mar 2011 11:17:40 -0500
> On Mon, Mar 07, 2011 at 03:58:46PM +0800, Amerigo Wang wrote:
>> V2: Move #ifdef CONFIG_PROC_FS into bonding.h, as suggested by David.
>>
>> bond_main.c is bloating, separate the procfs code out,
>> move them to bond_procfs.c
>>
>> Signed-off-by: WANG Cong <amwang@redhat.com>
>>
>
> Looks good and works as expected.
>
> Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
Applied, thanks everyone.
prev parent reply other threads:[~2011-03-09 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 7:58 [V2 Patch] bonding: move procfs code into bond_procfs.c Amerigo Wang
2011-03-07 7:49 ` Jiri Pirko
2011-03-07 16:17 ` Andy Gospodarek
2011-03-09 21:34 ` David Miller [this message]
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=20110309.133439.246540302.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amwang@redhat.com \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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).