From: David Miller <davem@davemloft.net>
To: dbanerje@akamai.com
Cc: j.vosburgh@gmail.com, vfalico@gmail.com,
gospo@cumulusnetworks.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] bonding: do not allow rlb updates to invalid mac
Date: Sun, 10 Apr 2016 22:26:33 -0400 (EDT) [thread overview]
Message-ID: <20160410.222633.1851379881977372838.davem@davemloft.net> (raw)
In-Reply-To: <1459974275-24944-1-git-send-email-dbanerje@akamai.com>
Please resubmit this patch series with a proper cover letter.
It should have "[PATCH 0/3] ..." as the subject line and explain
at a high level what your patch series is doing, how it is doing
it, and why it is doing it that way.
You must also be explicit about which of my trees your changes
are targetting.
Thanks.
prev parent reply other threads:[~2016-04-11 2:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 20:24 [PATCH 1/3] bonding: do not allow rlb updates to invalid mac Debabrata Banerjee
2016-04-06 20:24 ` [PATCH 2/3] bonding: don't request extraneous rlb updates Debabrata Banerjee
2016-04-06 20:24 ` [PATCH 3/3] bonding: use common broadcast addr checks Debabrata Banerjee
2016-04-11 2:26 ` 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=20160410.222633.1851379881977372838.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dbanerje@akamai.com \
--cc=gospo@cumulusnetworks.com \
--cc=j.vosburgh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).