From: Richard Cochran <richardcochran@gmail.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>, Yonghong Song <yhs@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Divya Koppera <Divya.Koppera@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] ptp: Add generic is_sync() function
Date: Sat, 5 Mar 2022 16:07:10 -0800 [thread overview]
Message-ID: <20220306000710.GA28085@hoboy.vegasvil.org> (raw)
In-Reply-To: <20220305112127.68529-1-kurt@linutronix.de>
On Sat, Mar 05, 2022 at 12:21:24PM +0100, Kurt Kanzenbach wrote:
> Hi,
>
> as multiple PHY drivers such as micrel or TI dp83640 need to inspect whether a
> given skb represents a PTP Sync message, provide a generic function for it. This
> avoids code duplication and can be reused by future PHY IEEE 1588 implementations.
>
> Thanks,
> Kurt
>
> Kurt Kanzenbach (3):
> ptp: Add generic PTP is_sync() function
> dp83640: Use generic ptp_msg_is_sync() function
> micrel: Use generic ptp_msg_is_sync() function
For the series:
Acked-by: Richard Cochran <richardcochran@gmail.com>
next prev parent reply other threads:[~2022-03-06 0:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 11:21 [PATCH net-next 0/3] ptp: Add generic is_sync() function Kurt Kanzenbach
2022-03-05 11:21 ` [PATCH net-next 1/3] ptp: Add generic PTP " Kurt Kanzenbach
2022-03-05 11:21 ` [PATCH net-next 2/3] dp83640: Use generic ptp_msg_is_sync() function Kurt Kanzenbach
2022-03-05 11:21 ` [PATCH net-next 3/3] micrel: " Kurt Kanzenbach
2022-03-07 7:38 ` Divya.Koppera
2022-03-06 0:07 ` Richard Cochran [this message]
2022-03-07 11:40 ` [PATCH net-next 0/3] ptp: Add generic is_sync() function patchwork-bot+netdevbpf
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=20220306000710.GA28085@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=Divya.Koppera@microchip.com \
--cc=andrew@lunn.ch \
--cc=andrii@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.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).