netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2014-05-19
Date: Mon, 19 May 2014 09:33:01 +0200	[thread overview]
Message-ID: <1400484782-16521-1-git-send-email-mkl@pengutronix.de> (raw)

Hello David,

this is a pull request for net/master, for the v3.15 release cycle, with a
single patch.

Oliver Hartkopp's patch removes a Kconfig option in the c_can driver, which was
added as a workaround during the v3.15 development. With all cleanup patches
this workaround is not needed anymore.

regards,
Marc

---

The following changes since commit 4f337ed5c014752b000f593182fdcfa3ecf0d166:

  MAINTAINERS: Pravin Shelar is Open vSwitch maintainer. (2014-05-18 21:04:39 -0400)

are available in the git repository at:

  git://gitorious.org/linux-can/linux-can.git tags/linux-can-fixes-for-3.15-20140519

for you to fetch changes up to 524369e2391f4b422d0efdd11d526a373a11a43a:

  can: c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig option (2014-05-19 09:03:06 +0200)

----------------------------------------------------------------
linux-can-fixes-for-3.15-20140519

----------------------------------------------------------------
Oliver Hartkopp (1):
      can: c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig option

 drivers/net/can/c_can/Kconfig |  7 -------
 drivers/net/can/c_can/c_can.c | 36 ------------------------------------
 2 files changed, 43 deletions(-)

             reply	other threads:[~2014-05-19  7:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19  7:33 Marc Kleine-Budde [this message]
2014-05-19  7:33 ` [PATCH] can: c_can: remove obsolete STRICT_FRAME_ORDERING Kconfig option Marc Kleine-Budde
2014-05-21  5:59 ` pull-request: can 2014-05-19 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=1400484782-16521-1-git-send-email-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).