From: David Miller <davem@davemloft.net>
To: nikolay@redhat.com
Cc: netdev@vger.kernel.org, andy@greyhouse.net, fubar@us.ibm.com
Subject: Re: [PATCH net-next v2] bonding: fix system hang due to fast igmp timer rescheduling
Date: Wed, 31 Jul 2013 17:05:47 -0700 (PDT) [thread overview]
Message-ID: <20130731.170547.33285495878732634.davem@davemloft.net> (raw)
In-Reply-To: <1375227846-17761-1-git-send-email-nikolay@redhat.com>
From: Nikolay Aleksandrov <nikolay@redhat.com>
Date: Wed, 31 Jul 2013 01:44:06 +0200
> From: "nikolay@redhat.com" <nikolay@redhat.com>
I don't think that "nikolay@redhat.com" is your name. :-)
Please fix this up and resubmit, thanks.
next prev parent reply other threads:[~2013-08-01 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 23:44 [PATCH net-next v2] bonding: fix system hang due to fast igmp timer rescheduling Nikolay Aleksandrov
2013-08-01 0:05 ` David Miller [this message]
2013-08-01 7:45 ` Nikolay Aleksandrov
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=20130731.170547.33285495878732634.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@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 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).