From: Jonathan Lemon <jonathan.lemon@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, richardcochran@gmail.com,
kernel-team@fb.com
Subject: [PATCH net-next v2 0/2] ptp: ocp: update devlink information
Date: Mon, 7 Mar 2022 16:05:33 -0800 [thread overview]
Message-ID: <20220308000536.2278-1-jonathan.lemon@gmail.com> (raw)
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.
drivers/ptp/ptp_ocp.c | 233 +++++++++++++++++++++++++-----------------
1 file changed, 140 insertions(+), 93 deletions(-)
--
2.31.1
next reply other threads:[~2022-03-08 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 0:05 Jonathan Lemon [this message]
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 ` [PATCH net-next v2 0/2] ptp: ocp: update devlink information 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=20220308000536.2278-1-jonathan.lemon@gmail.com \
--to=jonathan.lemon@gmail.com \
--cc=davem@davemloft.net \
--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 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).