From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org
Subject: Re: pull-request: can 2012-09-04
Date: Wed, 05 Sep 2012 15:12:51 -0400 (EDT) [thread overview]
Message-ID: <20120905.151251.344724883813764951.davem@davemloft.net> (raw)
In-Reply-To: <1346792142-17609-1-git-send-email-mkl@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Tue, 4 Sep 2012 22:55:41 +0200
> this patch is for the v3.6 release cycle. Benoît Locher fixed a repeated frame
> bug in the mcp251x driver. He implemented the workaround suggested by the
> errata sheet.
...
> git://gitorious.org/linux-can/linux-can.git fixes-for-3.6
Pulled, thanks Marc.
prev parent reply other threads:[~2012-09-05 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 20:55 pull-request: can 2012-09-04 Marc Kleine-Budde
2012-09-04 20:55 ` [PATCH] can: mcp251x: avoid repeated frame bug Marc Kleine-Budde
2012-09-05 19:12 ` David Miller [this message]
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=20120905.151251.344724883813764951.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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).