From: David Miller <davem@davemloft.net>
To: makc@redhat.com
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
vladislav.yasevich@hp.com
Subject: Re: [PATCH] sctp: deal with multiple COOKIE_ECHO chunks
Date: Sat, 17 Sep 2011 01:02:08 -0400 (EDT) [thread overview]
Message-ID: <20110917.010208.1774449645459771823.davem@davemloft.net> (raw)
In-Reply-To: <20084.9283.714998.398630@regina.usersys.redhat.com>
From: Max Matveev <makc@redhat.com>
Date: Sat, 17 Sep 2011 14:38:27 +1000
> Sorry about it - I did check it with checkpatch.pl and it was happy:
checkpatch doesn't look thoroughly for these things, use
something like "git apply --check --whitespace=error-all"
for validation instead.
prev parent reply other threads:[~2011-09-17 5:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 7:02 [PATCH] sctp: deal with multiple COOKIE_ECHO chunks Max Matveev
2011-09-16 21:17 ` David Miller
2011-09-17 4:38 ` Max Matveev
2011-09-17 5:02 ` 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=20110917.010208.1774449645459771823.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=makc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vladislav.yasevich@hp.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).