From: David Miller <davem@davemloft.net>
To: maheshb@google.com
Cc: j.vosburgh@gmail.com, andy@greyhouse.net, vfalico@gmail.com,
nikolay@redhat.com, maze@google.com, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH next v2] bonding: Code re-factoring for admin, oper-key operations
Date: Wed, 08 Apr 2015 12:12:29 -0400 (EDT) [thread overview]
Message-ID: <20150408.121229.21904699033169430.davem@davemloft.net> (raw)
In-Reply-To: <1428448571-1996-1-git-send-email-maheshb@google.com>
From: Mahesh Bandewar <maheshb@google.com>
Date: Tue, 7 Apr 2015 16:16:11 -0700
> This patch breaks the rich assignments into it's own statements
> and removes some duplicate code where admin-key, & oper-key are
> updated.
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
Applied.
prev parent reply other threads:[~2015-04-08 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 23:16 [PATCH next v2] bonding: Code re-factoring for admin, oper-key operations Mahesh Bandewar
2015-04-08 16:12 ` 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=20150408.121229.21904699033169430.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=maheshb@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=vfalico@gmail.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 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).