From: Heiko Carstens <hca@linux.ibm.com>
To: Sven Schnelle <svens@linux.ibm.com>,
Richard Cochran <richardcochran@gmail.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Richard Cochran <richardcochran@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Ricardo B. Marliere" <ricardo@marliere.net>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v3 0/2] PtP driver for s390 clocks
Date: Thu, 17 Oct 2024 11:46:06 +0200 [thread overview]
Message-ID: <20241017094606.6757-A-hca@linux.ibm.com> (raw)
In-Reply-To: <20241017060749.3893793-1-svens@linux.ibm.com>
On Thu, Oct 17, 2024 at 08:07:47AM +0200, Sven Schnelle wrote:
> Hi,
>
> these patches add support for using the s390 physical and TOD clock as ptp
> clock. To do so, the first patch adds a clock id to the s390 TOD clock,
> while the second patch adds the PtP driver itself.
...
> MAINTAINERS | 6 ++
> arch/s390/include/asm/stp.h | 1 +
> arch/s390/include/asm/timex.h | 6 ++
> arch/s390/kernel/time.c | 7 ++
> drivers/ptp/Kconfig | 11 +++
> drivers/ptp/Makefile | 1 +
> drivers/ptp/ptp_s390.c | 129 ++++++++++++++++++++++++++++++++
> include/linux/clocksource_ids.h | 1 +
> 8 files changed, 162 insertions(+)
> create mode 100644 drivers/ptp/ptp_s390.c
As far as I am concerned:
Acked-by: Heiko Carstens <hca@linux.ibm.com>
Richard, if this looks good for you too, how should this go upstream?
We could carry this via the s390 tree, if you want.
next prev parent reply other threads:[~2024-10-17 9:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 6:07 [PATCH v3 0/2] PtP driver for s390 clocks Sven Schnelle
2024-10-17 6:07 ` [PATCH v3 1/2] s390/time: Add clocksource id to TOD clock Sven Schnelle
2024-10-17 6:07 ` [PATCH v3 2/2] s390/time: Add PtP driver Sven Schnelle
2024-10-17 9:46 ` Heiko Carstens [this message]
2024-10-17 14:06 ` [PATCH v3 0/2] PtP driver for s390 clocks Richard Cochran
2024-10-17 14:06 ` Richard Cochran
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=20241017094606.6757-A-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ricardo@marliere.net \
--cc=richardcochran@gmail.com \
--cc=svens@linux.ibm.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