netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: David Miller <davem@davemloft.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: pull-request: can-next 2012-09-27
Date: Thu, 27 Sep 2012 16:43:42 +0200	[thread overview]
Message-ID: <5064661E.1000000@pengutronix.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

Hello David,

this pull request is for net-next, for the v3.7 release cycle.
AnilKumar Ch contributed a fix for a segfault in the c_can driver,
which is triggered by an earlier commit [1] in net-next (so no backport
is needed).

Marc

[1] 4cdd34b can: c_can: Add runtime PM support to Bosch C_CAN/D_CAN controller

---

The following changes since commit 842b08bbee448b2069aaebb7f18b40942ad2a1bd:

  ipconfig: fix trivial build error (2012-09-25 13:22:30 -0400)

are available in the git repository at:

  git://gitorious.org/linux-can/linux-can-next.git for-davem

for you to fetch changes up to c523530ce17defe6b28ccfe622c506488f430866:

  can: c_can: fix segfault during rmmod (2012-09-27 16:34:02 +0200)

----------------------------------------------------------------
AnilKumar Ch (1):
      can: c_can: fix segfault during rmmod

 drivers/net/can/c_can/c_can.c |    3 ---
 1 file changed, 3 deletions(-)

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

             reply	other threads:[~2012-09-27 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 14:43 Marc Kleine-Budde [this message]
2012-09-28 22:47 ` pull-request: can-next 2012-09-27 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=5064661E.1000000@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).