From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: pull-request: can-next 2013-03-27
Date: Wed, 27 Mar 2013 15:22:24 +0100 [thread overview]
Message-ID: <515300A0.2020105@pengutronix.de> (raw)
In-Reply-To: <5152FFB8.2000008@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On 03/27/2013 03:18 PM, Marc Kleine-Budde wrote:
> Hello David,
>
> this is a pull-request for net-next/master. It consists of three
> patches by Lars-Peter Clausen to clean up the mcp251x spi-can driver,
> two patches from Ludovic Desroches to bring device tree support to the
> at91_can driver and a patch by me to fix a sparse warning in the
> blackfin driver.
>
> regards,
> Marc
>
> ---
>
> The following changes since commit 6bdeaba47d87f48a3943b6899d6c6e6f17d52f1d:
>
> 6lowpan: use IEEE802154_ADDR_LEN instead of a magic number (2013-03-27 00:52:16 -0400)
>
> are available in the git repository at:
>
> git@gitorious.org:linux-can/linux-can-next.git testing
Doh! "testing" equals "for-davem" currently and git picked the "wrong"
tree. It should be:
git://gitorious.org/linux-can/linux-can-next.git for-davem
sorry,
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: 263 bytes --]
prev parent reply other threads:[~2013-03-27 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 14:18 pull-request: can-next 2013-03-27 Marc Kleine-Budde
2013-03-27 14:22 ` Marc Kleine-Budde [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=515300A0.2020105@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).