All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Y.b. Lu <yangbo.lu@nxp.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, mptcp@lists.linux.dev,
	richardcochran@gmail.com, davem@davemloft.net, kuba@kernel.org,
	mathew.j.martineau@linux.intel.com, matthieu.baerts@tessares.net,
	shuah@kernel.org, mkubecek@suse.cz, f.fainelli@gmail.com,
	andrew@lunn.ch, rui.sousa@nxp.com, sebastien.laveze@nxp.com
Subject: Re: [net-next, v5, 00/11] ptp: support virtual clocks and timestamping
Date: Thu, 01 Jul 2021 20:20:06 +0000	[thread overview]
Message-ID: <162517080630.9938.6469533434370383699.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210630081202.4423-1-yangbo.lu@nxp.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Wed, 30 Jun 2021 16:11:51 +0800 you wrote:
> Current PTP driver exposes one PTP device to user which binds network
> interface/interfaces to provide timestamping. Actually we have a way
> utilizing timecounter/cyclecounter to virtualize any number of PTP
> clocks based on a same free running physical clock for using.
> The purpose of having multiple PTP virtual clocks is for user space
> to directly/easily use them for multiple domains synchronization.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,01/11] ptp: add ptp virtual clock driver framework
    https://git.kernel.org/netdev/net/c/5d43f951b1ac
  - [net-next,v5,02/11] ptp: support ptp physical/virtual clocks conversion
    https://git.kernel.org/netdev/net/c/73f37068d540
  - [net-next,v5,03/11] ptp: track available ptp vclocks information
    https://git.kernel.org/netdev/net/c/44c494c8e30e
  - [net-next,v5,04/11] ptp: add kernel API ptp_get_vclocks_index()
    https://git.kernel.org/netdev/net/c/acb288e8047b
  - [net-next,v5,05/11] ethtool: add a new command for getting PHC virtual clocks
    https://git.kernel.org/netdev/net/c/c156174a6707
  - [net-next,v5,06/11] ptp: add kernel API ptp_convert_timestamp()
    https://git.kernel.org/netdev/net/c/895487a3a10f
  - [net-next,v5,07/11] mptcp: setsockopt: convert to mptcp_setsockopt_sol_socket_timestamping()
    https://git.kernel.org/netdev/net/c/6c9a0a0f2333
  - [net-next,v5,08/11] net: sock: extend SO_TIMESTAMPING for PHC binding
    https://git.kernel.org/netdev/net/c/d463126e23f1
  - [net-next,v5,09/11] net: socket: support hardware timestamp conversion to PHC bound
    https://git.kernel.org/netdev/net/c/d7c088265588
  - [net-next,v5,10/11] selftests/net: timestamping: support binding PHC
    https://git.kernel.org/netdev/net/c/2214d7032479
  - [net-next,v5,11/11] MAINTAINERS: add entry for PTP virtual clock driver
    https://git.kernel.org/netdev/net/c/5ce15f278333

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-07-01 20:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  8:11 [net-next, v5, 00/11] ptp: support virtual clocks and timestamping Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 01/11] ptp: add ptp virtual clock driver framework Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 02/11] ptp: support ptp physical/virtual clocks conversion Yangbo Lu
2021-07-04 10:25   ` [ptp] becdd56786: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2021-07-04 10:25     ` kernel test robot
2021-08-07  1:15   ` [net-next, v5, 02/11] ptp: support ptp physical/virtual clocks conversion Vinicius Costa Gomes
2021-08-07 14:22     ` Richard Cochran
2021-08-07 14:43       ` Vladimir Oltean
2021-08-07 20:56         ` Richard Cochran
2021-06-30  8:11 ` [net-next, v5, 03/11] ptp: track available ptp vclocks information Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 04/11] ptp: add kernel API ptp_get_vclocks_index() Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 05/11] ethtool: add a new command for getting PHC virtual clocks Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 06/11] ptp: add kernel API ptp_convert_timestamp() Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 07/11] mptcp: setsockopt: convert to mptcp_setsockopt_sol_socket_timestamping() Yangbo Lu
2021-06-30  8:11 ` [net-next, v5, 08/11] net: sock: extend SO_TIMESTAMPING for PHC binding Yangbo Lu
2021-07-04 13:33   ` Richard Cochran
2021-07-05  8:19     ` Y.b. Lu
2021-07-05 18:44       ` Richard Cochran
2021-06-30  8:12 ` [net-next, v5, 09/11] net: socket: support hardware timestamp conversion to PHC bound Yangbo Lu
2021-06-30  8:12 ` [net-next, v5, 10/11] selftests/net: timestamping: support binding PHC Yangbo Lu
2021-06-30  8:12 ` [net-next, v5, 11/11] MAINTAINERS: add entry for PTP virtual clock driver Yangbo Lu
2021-07-01 20:20 ` patchwork-bot+netdevbpf [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=162517080630.9938.6469533434370383699.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mkubecek@suse.cz \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=rui.sousa@nxp.com \
    --cc=sebastien.laveze@nxp.com \
    --cc=shuah@kernel.org \
    --cc=yangbo.lu@nxp.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.