All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Miller <davem@davemloft.net>
Cc: linux-sctp@vger.kernel.org, vyasevich@gmail.com, 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 07:17:04 +0000	[thread overview]
Message-ID: <506D37F0.5000804@6wind.com> (raw)
In-Reply-To: <20121003.162847.312544751568068374.davem@davemloft.net>

Le 03/10/2012 22:28, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Date: Wed,  3 Oct 2012 17:43:21 +0200
>
>> Just to avoid confusion when people only reads this prototype.
>>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
> I think we should apply this one, regardless of what happens
> to patch #2 in this series.
>
Yes, I catch it when working on the second patch, but I should send two seperate 
patches.

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Miller <davem@davemloft.net>
Cc: linux-sctp@vger.kernel.org, vyasevich@gmail.com, 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 09:17:04 +0200	[thread overview]
Message-ID: <506D37F0.5000804@6wind.com> (raw)
In-Reply-To: <20121003.162847.312544751568068374.davem@davemloft.net>

Le 03/10/2012 22:28, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Date: Wed,  3 Oct 2012 17:43:21 +0200
>
>> Just to avoid confusion when people only reads this prototype.
>>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
> I think we should apply this one, regardless of what happens
> to patch #2 in this series.
>
Yes, I catch it when working on the second patch, but I should send two seperate 
patches.

  reply	other threads:[~2012-10-04  7:17 UTC|newest]

Thread overview: 18+ 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 ` 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-03 15:43   ` Nicolas Dichtel
2012-10-04 17:03   ` Vlad Yasevich
2012-10-04 17:03     ` Vlad Yasevich
2012-10-04 19:54   ` David Miller
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-03 20:28   ` David Miller
2012-10-04  7:17   ` Nicolas Dichtel [this message]
2012-10-04  7:17     ` Nicolas Dichtel
2012-10-04 17:04 ` Vlad Yasevich
2012-10-04 17:04   ` Vlad Yasevich
2012-10-05  7:37   ` Nicolas Dichtel
2012-10-05  7:37     ` Nicolas Dichtel
2012-10-04 19:53 ` David Miller
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=506D37F0.5000804@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vyasevich@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 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.