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: pull-request: can 2020-11-18
Date: Wed, 18 Nov 2020 17:04:10 +0100 [thread overview]
Message-ID: <20201118160414.2731659-1-mkl@pengutronix.de> (raw)
Hello Jakub, hello David,
here's a pull request for net/master consisting of 4 patches for net/master,
Jimmy Assarsson provides two patches for the kvaser_pciefd and kvaser_usb
drivers, where the can_bittiming_const are fixed.
The next patch is by me and fixes an erroneous flexcan_transceiver_enable()
during bus-off recovery in the flexcan driver.
Jarkko Nikula's patch for the m_can driver fixes the IRQ handler to only
process the interrupts if the device is not suspended.
regards,
Marc
P.S.: Can you merge net/master into net-next/master after merging this pull
request?
---
The following changes since commit c09c8a27b9baa417864b9adc3228b10ae5eeec93:
ipv4: use IS_ENABLED instead of ifdef (2020-11-17 17:02:03 -0800)
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-5.10-20201118
for you to fetch changes up to a1f634463aaf2c94dfa13001dbdea011303124cc:
can: m_can: process interrupt only when not runtime suspended (2020-11-18 16:37:32 +0100)
----------------------------------------------------------------
linux-can-fixes-for-5.10-20201118
----------------------------------------------------------------
Jarkko Nikula (1):
can: m_can: process interrupt only when not runtime suspended
Jimmy Assarsson (2):
can: kvaser_pciefd: Fix KCAN bittiming limits
can: kvaser_usb: kvaser_usb_hydra: Fix KCAN bittiming limits
Marc Kleine-Budde (1):
can: flexcan: flexcan_chip_start(): fix erroneous flexcan_transceiver_enable() during bus-off recovery
drivers/net/can/flexcan.c | 18 +++++++++---------
drivers/net/can/kvaser_pciefd.c | 4 ++--
drivers/net/can/m_can/m_can.c | 2 ++
drivers/net/can/usb/kvaser_usb/kvaser_usb_hydra.c | 2 +-
4 files changed, 14 insertions(+), 12 deletions(-)
next reply other threads:[~2020-11-18 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 16:04 Marc Kleine-Budde [this message]
2020-11-18 16:04 ` [net 1/4] can: kvaser_pciefd: Fix KCAN bittiming limits Marc Kleine-Budde
2020-11-18 16:04 ` [net 2/4] can: kvaser_usb: kvaser_usb_hydra: " Marc Kleine-Budde
2020-11-18 16:04 ` [net 3/4] can: flexcan: flexcan_chip_start(): fix erroneous flexcan_transceiver_enable() during bus-off recovery Marc Kleine-Budde
2020-11-18 16:04 ` [net 4/4] can: m_can: process interrupt only when not runtime suspended Marc Kleine-Budde
2020-11-19 1:52 ` pull-request: can 2020-11-18 Jakub Kicinski
2020-11-19 7:10 ` 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=20201118160414.2731659-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;
as well as URLs for NNTP newsgroup(s).