From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2018-05-10
Date: Thu, 10 May 2018 18:47:47 +0200 [thread overview]
Message-ID: <20180510164749.20481-1-mkl@pengutronix.de> (raw)
Hello David,
this is a pull request for net/master consisting of 2 patches.
Both patches are from Lukas Wunner and fix two problems found in the hi311x CAN
driver under high load situations.
regards,
Marc
---
The following changes since commit 4a026da91caaa36004a53a844dd00959370ea8fc:
net/9p: correct some comment errors in 9p file system code (2018-05-10 08:21:53 -0400)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-4.17-20180510
for you to fetch changes up to 32bee8f48fa048a3198109de50e51c092507ff52:
can: hi311x: Work around TX complete interrupt erratum (2018-05-10 18:25:30 +0200)
----------------------------------------------------------------
linux-can-fixes-for-4.17-20180510
----------------------------------------------------------------
Lukas Wunner (2):
can: hi311x: Acquire SPI lock on ->do_get_berr_counter
can: hi311x: Work around TX complete interrupt erratum
drivers/net/can/spi/hi311x.c | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
next reply other threads:[~2018-05-10 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:47 Marc Kleine-Budde [this message]
2018-05-10 16:47 ` [PATCH 1/2] can: hi311x: Acquire SPI lock on ->do_get_berr_counter Marc Kleine-Budde
2018-05-10 16:47 ` [PATCH 2/2] can: hi311x: Work around TX complete interrupt erratum Marc Kleine-Budde
2018-05-10 21:58 ` pull-request: can 2018-05-10 David Miller
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=20180510164749.20481-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--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).