All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Linux Netdev List <netdev@vger.kernel.org>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>,
	Holger.Bechtold@gmx.net
Subject: request to queue "5d0f801 can: c_can: Fix RX message handling, handle lost message before EOB" for stable
Date: Sun, 24 Nov 2013 23:15:51 +0100	[thread overview]
Message-ID: <52927A97.2060601@pengutronix.de> (raw)

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

Hello David,

usually all relevant patches find their way (from my point of view,
magically :) to the stable trees, however in my last pull request to
net/master, which was merged in

    e9b51a1 Merge branch 'fixes-for-3.12' of
git://gitorious.org/linux-can/linux-can

there were two patches, both had stable on Cc. So far one has been added
to the stable queue, the other:

    5d0f801 can: c_can: Fix RX message handling, handle lost message
before EOB

is missing. Can you please queue, if not happened so far, that patch, too?

cheers,
Marc

-- 
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:[~2013-11-24 22:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 22:15 Marc Kleine-Budde [this message]
2013-11-24 22:48 ` request to queue "5d0f801 can: c_can: Fix RX message handling, handle lost message before EOB" for stable David Miller
2013-11-24 22:41   ` Marc Kleine-Budde
2013-11-24 23:00     ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2013-11-24 22:58 Marc Kleine-Budde
2013-11-25 21:05 ` Greg KH

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=52927A97.2060601@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Holger.Bechtold@gmx.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.