mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Austin, Alex (DCCG)" <alex.austin@amd.com>
To: netdev-bot+sashiko@kernel.org
Cc: ecree.xilinx@gmail.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
	pabeni@redhat.com, richardcochran@gmail.com,
	netdev@vger.kernel.org, linux-net-drivers@amd.com,
	linux-kernel@vger.kernel.org, alucerop@amd.com,
	pieter.jansen-van-vuuren@amd.com
Subject: Re: [PATCH net v3 1/3] sfc: ptp: drop the stale frequency reset in efx_ptp_start()
Date: Mon, 26 Oct 2026 11:05:30 +0000	[thread overview]
Message-ID: <387f0510-d3ed-4e12-9e70-8b6242a8e565@amd.com> (raw)
In-Reply-To: <179292676968.3134.7576333163086767429@kernel.org>


On 25/10/2026 11:12, netdev-bot+sashiko@kernel.org wrote:
> [Some people who received this message don't often get email from netdev-bot+sashiko@kernel.org. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> Thank you for your contribution! Sashiko AI review found 2 potential
> issue(s) to consider.
>
> Critical: 0 · High: 0 · Medium: 2 · Low: 0 (1)
>
> If you believe none of the issues are legitimate, please reply to each
> issue of Medium severity or higher and explain why the AI is wrong.
> If any of them are legitimate and you plan to respin, please let patchwork
> know by including "pw-bot: cr" as a separate line at the end of your reply
> (one such reply per series is enough).
>
> - [Medium] The fix leaves the forked Siena driver unfixed.
> - [Medium] The commit message understates the bug it fixes and has an
>   invalid Fixes: tag.
>
> Pre-existing issues:
> - [Low] This problem wasn't introduced by this patch, but the kernel-doc
>   for struct efx_ptp_data describes `@current_adjfreq: Current ppb…
>
> --
>

[...]

>
>> Fixes: ffe9554c17bf ("sfc: Add support for IEEE-1588 PTP")
> Is this hash right? ffe9554c17bf does not resolve to any commit. The commit
> with this subject appears to be 7c236c43b838, which the other patches in
> this series also use:
>
> Fixes: 7c236c43b838 ("sfc: Add support for IEEE-1588 PTP")


This is wrong. Will correct and respin.

pw-bot: cr



  reply	other threads:[~2026-10-26 11:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  9:15 [PATCH net v3 0/3] sfc: fix PTP synchronization races Alex Austin
2026-10-21  9:15 ` [PATCH net v3 1/3] sfc: ptp: drop the stale frequency reset in efx_ptp_start() Alex Austin
2026-10-25 11:12   ` netdev-bot+sashiko
2026-10-26 11:05     ` Austin, Alex (DCCG) [this message]
2026-10-21  9:15 ` [PATCH net v3 2/3] sfc: ptp: serialize host and MC synchronization transactions Alex Austin
2026-10-25 11:12   ` netdev-bot+sashiko
2026-10-21  9:15 ` [PATCH net v3 3/3] sfc: ptp: avoid racing PPS timestamp updates Alex Austin

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=387f0510-d3ed-4e12-9e70-8b6242a8e565@amd.com \
    --to=alex.austin@amd.com \
    --cc=alucerop@amd.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pieter.jansen-van-vuuren@amd.com \
    --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

all inboxes | Powered by JetHome®