All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <min.li.xe@renesas.com>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 net-next 1/3] ptp: idt82p33: add adjphase support
Date: Sat, 07 Nov 2020 21:20:05 +0000	[thread overview]
Message-ID: <160478400523.31399.554998376784709803.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1604634729-24960-1-git-send-email-min.li.xe@renesas.com>

Hello:

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

On Thu, 5 Nov 2020 22:52:07 -0500 you wrote:
> From: Min Li <min.li.xe@renesas.com>
> 
> Add idt82p33_adjphase() to support PHC write phase mode.
> 
> Changes since v1:
> -Fix broken build
> 
> [...]

Here is the summary with links:
  - [v4,net-next,1/3] ptp: idt82p33: add adjphase support
    https://git.kernel.org/netdev/net-next/c/e014ae39493f
  - [v4,net-next,2/3] ptp: idt82p33: use i2c_master_send for bus write
    https://git.kernel.org/netdev/net-next/c/e4c6eb68343f
  - [v4,net-next,3/3] ptp: idt82p33: optimize _idt82p33_adjfine
    https://git.kernel.org/netdev/net-next/c/6c196f36f524

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



      parent reply	other threads:[~2020-11-07 21:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  3:52 [PATCH v4 net-next 1/3] ptp: idt82p33: add adjphase support min.li.xe
2020-11-06  3:52 ` [PATCH v4 net-next 2/3] ptp: idt82p33: use i2c_master_send for bus write min.li.xe
2020-11-06  3:52 ` [PATCH v4 net-next 3/3] ptp: idt82p33: optimize _idt82p33_adjfine min.li.xe
2020-11-07 21:12 ` [PATCH v4 net-next 1/3] ptp: idt82p33: add adjphase support Jakub Kicinski
2020-11-07 21: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=160478400523.31399.554998376784709803.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 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.