From: patchwork-bot+netdevbpf@kernel.org
To: Min Li <min.li.xe@renesas.com>
Cc: richardcochran@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net 1/2] ptp: idt82p33: Add PTP_CLK_REQ_EXTTS support
Date: Fri, 25 Nov 2022 10:50:19 +0000 [thread overview]
Message-ID: <166937341938.11224.8741791396889501029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123195207.10260-1-min.li.xe@renesas.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 23 Nov 2022 14:52:06 -0500 you wrote:
> 82P33 family of chips can trigger TOD read/write by external
> signal from one of the IN12/13/14 pins, which are set user
> space programs by calling PTP_PIN_SETFUNC through ptp_ioctl
>
> Signed-off-by: Min Li <min.li.xe@renesas.com>
> ---
> drivers/ptp/ptp_idt82p33.c | 683 +++++++++++++++++++++++++++++++++----
> drivers/ptp/ptp_idt82p33.h | 20 +-
> 2 files changed, 640 insertions(+), 63 deletions(-)
Here is the summary with links:
- [net,1/2] ptp: idt82p33: Add PTP_CLK_REQ_EXTTS support
https://git.kernel.org/netdev/net-next/c/ad3cc7760dc4
- [net,2/2] ptp: idt82p33: remove PEROUT_ENABLE_OUTPUT_MASK
https://git.kernel.org/netdev/net-next/c/46da4aa2560f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-25 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 19:52 [PATCH net 1/2] ptp: idt82p33: Add PTP_CLK_REQ_EXTTS support Min Li
2022-11-23 19:52 ` [PATCH net 2/2] ptp: idt82p33: remove PEROUT_ENABLE_OUTPUT_MASK Min Li
2022-11-25 10:50 ` patchwork-bot+netdevbpf [this message]
2023-01-16 16:21 ` [PATCH net 1/2] ptp: idt82p33: Add PTP_CLK_REQ_EXTTS support Min Li
2023-01-17 17:13 ` Jakub Kicinski
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=166937341938.11224.8741791396889501029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min.li.xe@renesas.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).