All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Min Li <lnimi@hotmail.com>
Cc: richardcochran@gmail.com, lee@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Min Li <min.li.xe@renesas.com>
Subject: Re: [PATCH net-next v7 0/5] ptp: clockmatrix: support 32-bit address space
Date: Tue, 19 Mar 2024 12:15:28 +0100	[thread overview]
Message-ID: <Zflz0PK6mgQm1ZgO@nanopsycho> (raw)
In-Reply-To: <ZfloWPxw_iFJvLDs@nanopsycho>

Tue, Mar 19, 2024 at 11:26:32AM CET, jiri@resnulli.us wrote:
>Mon, Mar 18, 2024 at 06:32:08PM CET, lnimi@hotmail.com wrote:
>>From: Min Li <min.li.xe@renesas.com>
>>
>>The main porpose of this series is [PATCH 1/5], which is to support read/write
>>to the whole 32-bit address space. Other changes are increamental since
>>[PATCH 1/5].
>
>net-next is closed, send again next week.

Ah, different tree. Sorry.

>
>> 
>>
>>Min Li (5):
>>  ptp: clockmatrix: support 32-bit address space
>>  ptp: clockmatrix: set write phase timer to 0 when not in PCW mode
>>  ptp: clockmatrix: dco input-to-output delay is 20 FOD cycles + 8ns
>>  ptp: clockmatrix: Fix caps.max_adj to reflect
>>    DPLL_MAX_FREQ_OFFSET[MAX_FFO]
>>  ptp: clockmatrix: move register and firmware related definition to
>>    idt8a340_reg.h
>>
>> drivers/ptp/ptp_clockmatrix.c    | 120 ++++--
>> drivers/ptp/ptp_clockmatrix.h    |  66 +--
>> include/linux/mfd/idt8a340_reg.h | 664 ++++++++++++++++++-------------
>> 3 files changed, 482 insertions(+), 368 deletions(-)
>>
>>-- 
>>2.39.2
>>
>>

  reply	other threads:[~2024-03-19 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 17:32 [PATCH net-next v7 0/5] ptp: clockmatrix: support 32-bit address space Min Li
2024-03-19 10:26 ` Jiri Pirko
2024-03-19 11:15   ` Jiri Pirko [this message]
2024-03-21 18:04 ` Lee Jones
  -- strict thread matches above, loose matches on Subject: below --
2024-05-01 16:03 Min Li
2024-05-02  6:58 ` Horatiu Vultur
2024-05-03 14:06   ` Min Li

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=Zflz0PK6mgQm1ZgO@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnimi@hotmail.com \
    --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 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.