From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: linux-can@vger.kernel.org, davem@davemloft.net
Subject: pull-request: can 2013-04-12
Date: Fri, 12 Apr 2013 13:11:55 +0200 [thread overview]
Message-ID: <1365765117-28316-1-git-send-email-mkl@pengutronix.de> (raw)
Hello David,
here's another fix for the v3.9 release cycle, if not too late:
Christoph Fritz fixed the device tree property handling on little endian
systems in the sja1000 device tree driver. It was Mylene Josserand who noticed
that the mcp251x spi CAN driver cannot request its interrupt anymore, as the
driver is using a threaded interrupt handler without a primary one and without
specifying IRQF_ONESHOT (which is needed since v3.5). A patch by me fixes this
problem.
regards,
Marc
---
The following changes since commit 50bceae9bd3569d56744882f3012734d48a1d413:
tcp: Reallocate headroom if it would overflow csum_start (2013-04-11 18:12:41 -0400)
are available in the git repository at:
git://gitorious.org/linux-can/linux-can.git fixes-for-3.9
for you to fetch changes up to 0443de5fbf224abf41f688d8487b0c307dc5a4b4:
can: sja1000: fix handling on dt properties on little endian systems (2013-04-12 13:03:01 +0200)
----------------------------------------------------------------
Christoph Fritz (1):
can: sja1000: fix handling on dt properties on little endian systems
Marc Kleine-Budde (1):
can: mcp251x: add missing IRQF_ONESHOT to request_threaded_irq
drivers/net/can/mcp251x.c | 10 +++++++--
drivers/net/can/sja1000/sja1000_of_platform.c | 31 +++++++++++++--------------
2 files changed, 23 insertions(+), 18 deletions(-)
next reply other threads:[~2013-04-12 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 11:11 Marc Kleine-Budde [this message]
2013-04-12 11:11 ` [PATCH 1/2] can: mcp251x: add missing IRQF_ONESHOT to request_threaded_irq Marc Kleine-Budde
2013-04-12 11:11 ` [PATCH 2/2] can: sja1000: fix handling on dt properties on little endian systems Marc Kleine-Budde
2013-04-12 18:30 ` pull-request: can 2013-04-12 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=1365765117-28316-1-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--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).