All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH v6 net-next 0/7] Extend socket timestamping API
Date: Fri, 19 May 2017 22:15:27 +0200	[thread overview]
Message-ID: <20170519201527.GA19150@localhost.localdomain> (raw)
In-Reply-To: <20170519155241.15817-1-mlichvar@redhat.com>

On Fri, May 19, 2017 at 05:52:34PM +0200, Miroslav Lichvar wrote:
> Changes v5->v6:
> - fixed skb_is_swtx_tstamp() when OPT_TX_SWHW is disabled and improved
>   its description
> - improved OPT_PKTINFO documentation
> - improved scm_timestamping documentation

For the series:

Acked-by: Richard Cochran <richardcochran@gmail.com>

  parent reply	other threads:[~2017-05-19 20:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 15:52 [PATCH v6 net-next 0/7] Extend socket timestamping API Miroslav Lichvar
2017-05-19 15:52 ` [PATCH v6 net-next 1/7] net: define receive timestamp filter for NTP Miroslav Lichvar
2017-05-19 15:52 ` [PATCH v6 net-next 2/7] net: ethernet: update drivers to handle HWTSTAMP_FILTER_NTP_ALL Miroslav Lichvar
2017-05-19 15:52 ` [PATCH v6 net-next 3/7] net: add function to retrieve original skb device using NAPI ID Miroslav Lichvar
2017-05-19 15:52 ` [PATCH v6 net-next 4/7] net: add new control message for incoming HW-timestamped packets Miroslav Lichvar
2017-05-19 15:52 ` [PATCH v6 net-next 5/7] net: fix documentation of struct scm_timestamping Miroslav Lichvar
2017-05-19 15:59   ` Willem de Bruijn
2017-05-19 15:52 ` [PATCH v6 net-next 6/7] net: allow simultaneous SW and HW transmit timestamping Miroslav Lichvar
2017-05-19 16:00   ` Willem de Bruijn
2017-05-19 15:52 ` [PATCH v6 net-next 7/7] net: ethernet: update drivers to make both SW and HW TX timestamps Miroslav Lichvar
2017-05-19 20:15 ` Richard Cochran [this message]
2017-05-21 17:38 ` [PATCH v6 net-next 0/7] Extend socket timestamping API 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=20170519201527.GA19150@localhost.localdomain \
    --to=richardcochran@gmail.com \
    --cc=mlichvar@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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.