All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dcaratti@redhat.com
Cc: borisp@mellanox.com, jakub.kicinski@netronome.com,
	eric.dumazet@gmail.com, aviadye@mellanox.com, davejwatson@fb.com,
	john.fastabend@gmail.com, matthieu.baerts@tessares.net,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] net: tls: add socket diag
Date: Sat, 31 Aug 2019 23:44:42 -0700 (PDT)	[thread overview]
Message-ID: <20190831.234442.1136062804304759437.davem@davemloft.net> (raw)
In-Reply-To: <cover.1567158431.git.dcaratti@redhat.com>

From: Davide Caratti <dcaratti@redhat.com>
Date: Fri, 30 Aug 2019 12:25:46 +0200

> The current kernel does not provide any diagnostic tool, except
> getsockopt(TCP_ULP), to know more about TCP sockets that have an upper
> layer protocol (ULP) on top of them. This series extends the set of
> information exported by INET_DIAG_INFO, to include data that are
> specific to the ULP (and that might be meaningful for debug/testing
> purposes).
 ...

Series applied, thanks Davide.

      parent reply	other threads:[~2019-09-01  6:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 10:25 [PATCH net-next v3 0/3] net: tls: add socket diag Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 1/3] net/tls: use RCU protection on icsk->icsk_ulp_data Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 2/3] tcp: ulp: add functions to dump ulp-specific information Davide Caratti
2019-08-30 10:25 ` [PATCH net-next v3 3/3] net: tls: export protocol version, cipher, tx_conf/rx_conf to socket diag Davide Caratti
2019-08-30 22:45   ` Jakub Kicinski
2019-09-01  6:44 ` 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=20190831.234442.1136062804304759437.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=aviadye@mellanox.com \
    --cc=borisp@mellanox.com \
    --cc=davejwatson@fb.com \
    --cc=dcaratti@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jakub.kicinski@netronome.com \
    --cc=john.fastabend@gmail.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=netdev@vger.kernel.org \
    /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.