All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Phil Sutter <phil@nwl.cc>
Cc: David Miller <davem@davemloft.net>,
	Xin Long <lucien.xin@gmail.com>,
	netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH v3 0/3] sctp_diag: A bunch of fixes for upcoming 'ss' support
Date: Thu, 04 Aug 2016 12:36:17 +0000	[thread overview]
Message-ID: <20160804123617.GG2967@localhost.localdomain> (raw)
In-Reply-To: <1470305517-31880-1-git-send-email-phil@nwl.cc>

On Thu, Aug 04, 2016 at 12:11:54PM +0200, Phil Sutter wrote:
> The following series contains a number of fixes necessary to make my yet
> unpublished 'ss' support patch functional.
> 
> Changes since v1:
> - Fixed patch 2/3
> - Rebased whole series onto current net-next/master
> 
> Changes since v2:
> - Improved description of patch 2/3
> 
> Phil Sutter (3):
>   sctp: Export struct sctp_info to userspace
>   sctp_diag: Fix T3_rtx timer export
>   sctp_diag: Respect ss adding TCPF_CLOSE to idiag_states
> 

Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

Thanks!


WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Phil Sutter <phil@nwl.cc>
Cc: David Miller <davem@davemloft.net>,
	Xin Long <lucien.xin@gmail.com>,
	netdev@vger.kernel.org, linux-sctp@vger.kernel.org
Subject: Re: [PATCH v3 0/3] sctp_diag: A bunch of fixes for upcoming 'ss' support
Date: Thu, 4 Aug 2016 09:36:17 -0300	[thread overview]
Message-ID: <20160804123617.GG2967@localhost.localdomain> (raw)
In-Reply-To: <1470305517-31880-1-git-send-email-phil@nwl.cc>

On Thu, Aug 04, 2016 at 12:11:54PM +0200, Phil Sutter wrote:
> The following series contains a number of fixes necessary to make my yet
> unpublished 'ss' support patch functional.
> 
> Changes since v1:
> - Fixed patch 2/3
> - Rebased whole series onto current net-next/master
> 
> Changes since v2:
> - Improved description of patch 2/3
> 
> Phil Sutter (3):
>   sctp: Export struct sctp_info to userspace
>   sctp_diag: Fix T3_rtx timer export
>   sctp_diag: Respect ss adding TCPF_CLOSE to idiag_states
> 

Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

Thanks!

  parent reply	other threads:[~2016-08-04 12:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 10:11 [PATCH v3 0/3] sctp_diag: A bunch of fixes for upcoming 'ss' support Phil Sutter
2016-08-04 10:11 ` Phil Sutter
2016-08-04 10:11 ` [PATCH v3 1/3] sctp: Export struct sctp_info to userspace Phil Sutter
2016-08-04 10:11   ` Phil Sutter
2016-08-04 13:33   ` Neil Horman
2016-08-04 13:33     ` Neil Horman
2016-08-04 14:40     ` Phil Sutter
2016-08-04 14:40       ` Phil Sutter
2016-08-04 10:11 ` [PATCH v3 2/3] sctp_diag: Fix T3_rtx timer export Phil Sutter
2016-08-04 10:11   ` Phil Sutter
2016-08-04 10:11 ` [PATCH v3 3/3] sctp_diag: Respect ss adding TCPF_CLOSE to idiag_states Phil Sutter
2016-08-04 10:11   ` Phil Sutter
2016-08-04 12:36 ` Marcelo Ricardo Leitner [this message]
2016-08-04 12:36   ` [PATCH v3 0/3] sctp_diag: A bunch of fixes for upcoming 'ss' support Marcelo Ricardo Leitner

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=20160804123617.GG2967@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=phil@nwl.cc \
    /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.