From: Daniel Borkmann <dborkman@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH net-next] net: sctp: sctp_verify_init: clean up mandatory checks and add comment
Date: Tue, 27 Aug 2013 13:59:42 +0000 [thread overview]
Message-ID: <521CB0CE.3000806@redhat.com> (raw)
In-Reply-To: <20130827134302.GB7619@hmsreliant.think-freely.org>
On 08/27/2013 03:43 PM, Neil Horman wrote:
> nit: If we're making this easier to review, I think the above would be easier to
> read if it said:
> Note: Initial TSN is also mandatory, but is not checked here since the valid
> range is 0..2**(32-1)
Ok, will send a v2 in a moment.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH net-next] net: sctp: sctp_verify_init: clean up mandatory checks and add comment
Date: Tue, 27 Aug 2013 15:59:42 +0200 [thread overview]
Message-ID: <521CB0CE.3000806@redhat.com> (raw)
In-Reply-To: <20130827134302.GB7619@hmsreliant.think-freely.org>
On 08/27/2013 03:43 PM, Neil Horman wrote:
> nit: If we're making this easier to review, I think the above would be easier to
> read if it said:
> Note: Initial TSN is also mandatory, but is not checked here since the valid
> range is 0..2**(32-1)
Ok, will send a v2 in a moment.
next prev parent reply other threads:[~2013-08-27 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 13:23 [PATCH net-next] net: sctp: sctp_verify_init: clean up mandatory checks and add comment Daniel Borkmann
2013-08-27 13:23 ` Daniel Borkmann
2013-08-27 13:43 ` Neil Horman
2013-08-27 13:43 ` Neil Horman
2013-08-27 13:59 ` Daniel Borkmann [this message]
2013-08-27 13:59 ` Daniel Borkmann
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=521CB0CE.3000806@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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.