All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ding Tianhong <dingtianhong@huawei.com>
To: Veaceslav Falico <vfalico@redhat.com>, <netdev@vger.kernel.org>
Cc: Jay Vosburgh <fubar@us.ibm.com>, Andy Gospodarek <andy@greyhouse.net>
Subject: Re: [PATCH net-next 0/3] bonding: cleanup bond_3ad.c
Date: Thu, 9 Jan 2014 09:36:39 +0800	[thread overview]
Message-ID: <52CDFD27.50400@huawei.com> (raw)
In-Reply-To: <1389196008-28578-1-git-send-email-vfalico@redhat.com>

On 2014/1/8 23:46, Veaceslav Falico wrote:
> It's a huge mess there currently - and, thus, really hard to read and
> debug.
> 
> This is the first series, and doesn't change the logic at all, only makes
> it a bit more readable.
> 
> CC: Jay Vosburgh <fubar@us.ibm.com>
> CC: Andy Gospodarek <andy@greyhouse.net>
> Signed-off-by: Veaceslav Falico <vfalico@redhat.com>
> 
> ---
>  drivers/net/bonding/bond_3ad.c | 731 +++++++++++++++++++++--------------------
>  1 file changed, 366 insertions(+), 365 deletions(-)
> 

Great work!

Tested-by: Ding Tianhong <dingtianhong@huawei.com>

  parent reply	other threads:[~2014-01-09  1:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 15:46 [PATCH net-next 0/3] bonding: cleanup bond_3ad.c Veaceslav Falico
2014-01-08 15:46 ` [PATCH net-next 1/3] bonding: clean up style for bond_3ad.c Veaceslav Falico
2014-01-08 15:46 ` [PATCH net-next 2/3] bonding: convert 3ad to use pr_warn instead of pr_warning Veaceslav Falico
2014-01-08 15:46 ` [PATCH net-next 3/3] bonding: remove dead code from 3ad Veaceslav Falico
2014-01-09  1:36 ` Ding Tianhong [this message]
2014-01-10 23:06 ` [PATCH net-next 0/3] bonding: cleanup bond_3ad.c David Miller
2014-01-12 13:27   ` Veaceslav Falico
2014-01-12 22:36     ` David Miller
2014-01-12 22:44       ` David Miller
2014-01-13  7:57         ` Veaceslav Falico

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=52CDFD27.50400@huawei.com \
    --to=dingtianhong@huawei.com \
    --cc=andy@greyhouse.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=vfalico@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.