All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>
To: netdev-bot+sinfo@kernel.org
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Jose Abreu <Jose.Abreu@synopsys.com>,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net v3] net: stmmac: propagate PTP addend and system time programming errors
Date: Thu, 1 Oct 2026 11:38:47 +0200	[thread overview]
Message-ID: <ar4qJ9gI3dk4S3yw@lore-desk> (raw)
In-Reply-To: <179068769042.31693.17699965363723906103@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]

> Hi!
> 
> This is an automated message. This series looks like a fix, but its
> commit messages seem to be missing some information:
> 
>  - How the issue was discovered, e.g. hit in production, hit during
>    development, syzbot report, manual code inspection, LLM or static
>    analysis tool scan.

I discovered the issue during manual code inspection

> 
>  - Whether the issue was actually triggered, or is only theoretical
>    (e.g. found by code inspection). If it was triggered please include
>    the symptoms, like the stack trace or error messages.

This issue is theoretical, I have never triggered it on a running device.

> 
>  - What hardware the change was tested on. For driver fixes please
>    mention the device (and if relevant firmware version) used for
>    testing, or say that the change was not tested on real hardware.

I tested the modified codebase on a qualcomm rb3-gen2 board.

Regards,
Lorenzo

> 
> Please do not repost the series just to address the above. Instead,
> reply to this email with the missing information, so that reviewers
> can take it into account. If the series needs another revision for
> other reasons, please include the information in the commit messages
> then.
> 
> The evaluation is done by an LLM so it may be wrong, if you think
> that is the case please reply and explain.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-10-01  9:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 13:10 [PATCH net v3] net: stmmac: propagate PTP addend and system time programming errors Lorenzo Bianconi
2026-09-29 13:14 ` netdev-bot+sinfo
2026-10-01  9:38   ` Lorenzo Bianconi [this message]
2026-10-01  9:18 ` Maxime Chevallier
2026-10-02  1:13 ` netdev-bot+sashiko
2026-10-02  9:40 ` patchwork-bot+netdevbpf
2026-10-05 20:16 ` Anirudh Srinivasan
2026-10-05 20:16   ` Anirudh Srinivasan
2026-10-05 21:53   ` Lorenzo Bianconi
2026-10-05 21:53     ` Lorenzo Bianconi
2026-10-05 22:40     ` Anirudh Srinivasan
2026-10-05 22:40       ` Anirudh Srinivasan
2026-10-06  6:57       ` Lorenzo Bianconi
2026-10-06  6:57         ` Lorenzo Bianconi
2026-10-06 14:06         ` Anirudh Srinivasan
2026-10-06 14:06           ` Anirudh Srinivasan
2026-10-06 14:33           ` Lorenzo Bianconi
2026-10-06 14:33             ` Lorenzo Bianconi
2026-10-06 15:12             ` Anirudh Srinivasan
2026-10-06 15:12               ` Anirudh Srinivasan
2026-10-06 15:28               ` Maxime Chevallier
2026-10-06 15:28                 ` Maxime Chevallier
2026-10-06 15:50                 ` Anirudh Srinivasan
2026-10-06 15:50                   ` Anirudh Srinivasan
2026-10-06  1:23     ` Jakub Kicinski
2026-10-06  1:23       ` Jakub Kicinski

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=ar4qJ9gI3dk4S3yw@lore-desk \
    --to=lorenzo.bianconi@oss.qualcomm.com \
    --cc=Jose.Abreu@synopsys.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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.