From: Vlad Yasevich <vyasevich@gmail.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] sctp: fix a typo in prototype of __sctp_rcv_lookup()
Date: Thu, 04 Oct 2012 13:04:16 -0400 [thread overview]
Message-ID: <506DC190.6050407@gmail.com> (raw)
In-Reply-To: <1349279002-4008-1-git-send-email-nicolas.dichtel@6wind.com>
On 10/03/2012 11:43 AM, Nicolas Dichtel wrote:
> Just to avoid confusion when people only reads this prototype.
>
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> ---
> net/sctp/input.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/sctp/input.c b/net/sctp/input.c
> index 25dfe73..8bd3c27 100644
> --- a/net/sctp/input.c
> +++ b/net/sctp/input.c
> @@ -68,8 +68,8 @@
> static int sctp_rcv_ootb(struct sk_buff *);
> static struct sctp_association *__sctp_rcv_lookup(struct net *net,
> struct sk_buff *skb,
> - const union sctp_addr *laddr,
> const union sctp_addr *paddr,
> + const union sctp_addr *laddr,
> struct sctp_transport **transportp);
> static struct sctp_endpoint *__sctp_rcv_lookup_endpoint(struct net *net,
> const union sctp_addr *laddr);
>
Wow, this must have been very old...
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
next prev parent reply other threads:[~2012-10-04 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 15:43 [RFC PATCH 1/2] sctp: fix a typo in prototype of __sctp_rcv_lookup() Nicolas Dichtel
2012-10-03 15:43 ` [RFC PATCH 2/2] sctp: check src addr when processing SACK to update transport state Nicolas Dichtel
2012-10-04 17:03 ` Vlad Yasevich
2012-10-04 19:54 ` David Miller
2012-10-03 20:28 ` [RFC PATCH 1/2] sctp: fix a typo in prototype of __sctp_rcv_lookup() David Miller
2012-10-04 7:17 ` Nicolas Dichtel
2012-10-04 17:04 ` Vlad Yasevich [this message]
2012-10-05 7:37 ` Nicolas Dichtel
2012-10-04 19:53 ` David Miller
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=506DC190.6050407@gmail.com \
--to=vyasevich@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.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).