From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
haibo.chen@nxp.com, stable@kernel.org
Subject: Re: [PATCH net 1/2] can: dev: keep the max bitrate error at 5%
Date: Tue, 10 Mar 2026 14:20:06 +0000 [thread overview]
Message-ID: <177315240680.2324285.3081385915384897372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260310103547.2299403-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Tue, 10 Mar 2026 11:30:34 +0100 you wrote:
> From: Haibo Chen <haibo.chen@nxp.com>
>
> Commit b360a13d44db ("can: dev: print bitrate error with two decimal
> digits") changed calculation of the bit rate error from on-tenth of a
> percent to on-hundredth of a percent, but forgot to adjust the scale of the
> CAN_CALC_MAX_ERROR constant.
>
> [...]
Here is the summary with links:
- [net,1/2] can: dev: keep the max bitrate error at 5%
https://git.kernel.org/netdev/net/c/1eea46908c57
- [net,2/2] can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value
https://git.kernel.org/netdev/net/c/47bba09b14fa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-03-10 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 10:30 [PATCH net 0/2] pull-request: can 2026-03-10 Marc Kleine-Budde
2026-03-10 10:30 ` [PATCH net 1/2] can: dev: keep the max bitrate error at 5% Marc Kleine-Budde
2026-03-10 14:20 ` patchwork-bot+netdevbpf [this message]
2026-03-10 10:30 ` [PATCH net 2/2] can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value Marc Kleine-Budde
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=177315240680.2324285.3081385915384897372.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.org \
/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