From: sashiko-bot@kernel.org
To: "Alok Tiwari" <alok.a.tiwari@oracle.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next] ice: correct PTP register access debug messages
Date: Mon, 12 Oct 2026 11:37:15 +0000 [thread overview]
Message-ID: <sashiko-outbox-168021@kernel.org> (raw)
In-Reply-To: <20261011113545.16718-1-alok.a.tiwari@oracle.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] ice: missing trailing newline in debug message for threshold write failure
--
commit 3dfc5e0655da8eeda86700792eb12011c421ed4e
Author: Alok Tiwari <alok.a.tiwari@oracle.com>
ice: correct PTP register access debug messages
This commit updates the debug message for PHY_VENDOR_TXLANE_THRESH to
report a write failure rather than a read failure. It also intends to fix
newline placement in PHY register read and threshold write failure
messages.
> diff --git a/drivers/net/ethernet/intel/ice/ice_ptp_hw.c b/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
> index 3a41c711e751b..289e0b3ef6ae9 100644
> --- a/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
> +++ b/drivers/net/ethernet/intel/ice/ice_ptp_hw.c
> @@ -1529,7 +1529,7 @@ static int ice_phy_cfg_parpcs_eth56g(struct ice_hw *hw, u8 port)
> err = ice_write_xpcs_reg_eth56g(hw, port, PHY_VENDOR_TXLANE_THRESH,
> ICE_ETH56G_NOMINAL_THRESH4);
> if (err) {
> - ice_debug(hw, ICE_DBG_PTP, "Failed to read VENDOR_TXLANE_THRESH, status: %d",
> + ice_debug(hw, ICE_DBG_PTP, "Failed to write VENDOR_TXLANE_THRESH, status: %d",
> err);
[Severity: Low]
In ice_phy_cfg_parpcs_eth56g(), is this missing a newline at the end of the
format string? The commit message indicates that it fixes newline placement
for the threshold write failure message, but the modified format string
still lacks a trailing newline when ice_write_xpcs_reg_eth56g() fails while
updating PHY_VENDOR_TXLANE_THRESH. Should a \n be appended to the string
here?
> return err;
> }
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261011113545.16718-1-alok.a.tiwari@oracle.com?part=1
next prev parent reply other threads:[~2026-10-12 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 11:35 [PATCH net-next] ice: correct PTP register access debug messages Alok Tiwari
2026-10-12 9:04 ` Loktionov, Aleksandr
2026-10-12 11:37 ` sashiko-bot [this message]
2026-10-13 22:44 ` Tony Nguyen
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=sashiko-outbox-168021@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alok.a.tiwari@oracle.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=sashiko-reviews@lists.linux.dev \
/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