From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de
Subject: [PATCH net 0/2] pull-request: can 2026-03-10
Date: Tue, 10 Mar 2026 11:30:33 +0100 [thread overview]
Message-ID: <20260310103547.2299403-1-mkl@pengutronix.de> (raw)
Hello netdev-team,
this is a pull request of 2 patches for net/main.
Haibo Chen's patch fixes the maximum allowed bit rate error, which was
broken in v6.19.
Wenyuan Li contributes a patch for the hi311x driver that adds missing
error checking in the caller of the hi3110_power_enable() function,
hi3110_open().
regards,
Marc
---
The following changes since commit e3f5e0f22cfc2371e7471c9fd5b4da78f9df7c69:
mctp: i2c: fix skb memory leak in receive path (2026-03-10 11:10:55 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-7.0-20260310
for you to fetch changes up to 47bba09b14fa21712398febf36cb14fd4fc3bded:
can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value (2026-03-10 11:12:52 +0100)
----------------------------------------------------------------
linux-can-fixes-for-7.0-20260310
----------------------------------------------------------------
Haibo Chen (1):
can: dev: keep the max bitrate error at 5%
Wenyuan Li (1):
can: hi311x: hi3110_open(): add check for hi3110_power_enable() return value
drivers/net/can/dev/calc_bittiming.c | 2 +-
drivers/net/can/spi/hi311x.c | 5 ++++-
2 files changed, 5 insertions(+), 2 deletions(-)
next reply other threads:[~2026-03-10 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 10:30 Marc Kleine-Budde [this message]
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
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=20260310103547.2299403-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.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