All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Piergiorgio Beruto <piergiorgio.beruto@gmail.com>
Cc: peppe.cavallaro@st.com, alexandre.torgue@foss.st.com,
	joabreu@synopsys.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
	richardcochran@gmail.com, julien.beraud@orolia.com,
	netdev@vger.kernel.org, andrew@lunn.ch
Subject: Re: [PATCH v2 net 1/1] stmmac: fix potential division by 0
Date: Mon, 12 Dec 2022 23:20:15 +0000	[thread overview]
Message-ID: <167088721582.27199.17800143260465196314.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <de4c64ccac9084952c56a06a8171d738604c4770.1670678513.git.piergiorgio.beruto@gmail.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Sat, 10 Dec 2022 23:37:22 +0100 you wrote:
> When the MAC is connected to a 10 Mb/s PHY and the PTP clock is derived
> from the MAC reference clock (default), the clk_ptp_rate becomes too
> small and the calculated sub second increment becomes 0 when computed by
> the stmmac_config_sub_second_increment() function within
> stmmac_init_tstamp_counter().
> 
> Therefore, the subsequent div_u64 in stmmac_init_tstamp_counter()
> operation triggers a divide by 0 exception as shown below.
> 
> [...]

Here is the summary with links:
  - [v2,net,1/1] stmmac: fix potential division by 0
    https://git.kernel.org/netdev/net/c/ede5a389852d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-12-12 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 13:37 [PATCH v2 net 1/1] stmmac: fix potential division by 0 Piergiorgio Beruto
2022-12-10 22:37 ` Piergiorgio Beruto
2022-12-11 11:18 ` Andrew Lunn
2022-12-12 23:20 ` 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=167088721582.27199.17800143260465196314.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=joabreu@synopsys.com \
    --cc=julien.beraud@orolia.com \
    --cc=kuba@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=peppe.cavallaro@st.com \
    --cc=piergiorgio.beruto@gmail.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.