From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Lemon <jonathan.lemon@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
richardcochran@gmail.com, kernel-team@fb.com
Subject: Re: [PATCH net-next v2 0/2] ptp: ocp: update devlink information
Date: Wed, 09 Mar 2022 11:10:11 +0000 [thread overview]
Message-ID: <164682421119.10972.15834919116382444719.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220308000536.2278-1-jonathan.lemon@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 7 Mar 2022 16:05:33 -0800 you wrote:
> Both of these patches update the information displayed via devlink.
>
> v1 -> v2: remove board.manufacture information
>
> Jonathan Lemon (2):
> ptp: ocp: add nvmem interface for accessing eeprom
> ptp: ocp: Update devlink firmware display path.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] ptp: ocp: add nvmem interface for accessing eeprom
(no matching commit)
- [net-next,v2,2/2] ptp: ocp: Update devlink firmware display path.
https://git.kernel.org/netdev/net-next/c/b0ca789ade4e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-09 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 0:05 [PATCH net-next v2 0/2] ptp: ocp: update devlink information Jonathan Lemon
2022-03-08 0:05 ` [PATCH net-next v2 1/2] ptp: ocp: add nvmem interface for accessing eeprom Jonathan Lemon
2022-03-08 0:05 ` [PATCH net-next v2 2/2] ptp: ocp: Update devlink firmware display path Jonathan Lemon
2022-03-09 11:10 ` 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=164682421119.10972.15834919116382444719.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jonathan.lemon@gmail.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--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.