netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: linux-can@vger.kernel.org
Subject: pull-request: can 2013-01-26
Date: Sat, 26 Jan 2013 17:33:24 +0100	[thread overview]
Message-ID: <1359218007-18586-1-git-send-email-mkl@pengutronix.de> (raw)

Hello David,

here's a patch for net for the v3.8 release cycle. Olivier Sobrie found and
fixed a problem in the can error frame generation of three drivers (c_can,
pch_can and ti_hecc).

regards,
Marc

---

The following changes since commit 5d0feaff230c0abfe4a112e6f09f096ed99e0b2d:

  r8169: remove the obsolete and incorrect AMD workaround (2013-01-23 13:51:47 -0500)

are available in the git repository at:

  git://gitorious.org/linux-can/linux-can.git fixes-for-3.8

for you to fetch changes up to ee50e135aeb048b90fab662e661c58b67341830b:

  can: pch_can: fix invalid error codes (2013-01-26 17:13:41 +0100)

----------------------------------------------------------------
Olivier Sobrie (3):
      can: c_can: fix invalid error codes
      can: ti_hecc: fix invalid error codes
      can: pch_can: fix invalid error codes

 drivers/net/can/c_can/c_can.c |    4 ++--
 drivers/net/can/pch_can.c     |    2 +-
 drivers/net/can/ti_hecc.c     |    4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)



             reply	other threads:[~2013-01-26 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26 16:33 Marc Kleine-Budde [this message]
2013-01-26 16:33 ` [PATCH 1/3] can: c_can: fix invalid error codes Marc Kleine-Budde
2013-01-26 16:33 ` [PATCH 2/3] can: ti_hecc: " Marc Kleine-Budde
2013-01-26 16:33 ` [PATCH 3/3] can: pch_can: " Marc Kleine-Budde
2013-01-27  5:48 ` pull-request: can 2013-01-26 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=1359218007-18586-1-git-send-email-mkl@pengutronix.de \
    --to=mkl@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).