public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp•net>
To: davem@davemloft•net
Cc: Marc Kleine-Budde <mkl@pengutronix•de>,
	Linux Netdev List <netdev@vger•kernel.org>,
	"linux-can@vger•kernel.org" <linux-can@vger•kernel.org>
Subject: Re: pull-request: can-next 2012-06-04
Date: Wed, 06 Jun 2012 20:02:35 +0200	[thread overview]
Message-ID: <4FCF9B3B.1070105@hartkopp.net> (raw)
In-Reply-To: <4FCCD9A8.7030207@pengutronix.de>

Hello Dave,

i think there was a confusion about

	linux-can and linux-can-next

pull requests that overlapped in the mail traffic that day.

The pull request of linux-can-next is still pending.

git://gitorious.org/linux-can/linux-can-next.git master

Regards,
Oliver



On 04.06.2012 17:52, Marc Kleine-Budde wrote:

> On 06/04/2012 12:52 AM, Marc Kleine-Budde wrote:
>> Hello David,
>>
>> here are the first patches for net-next, they add power management
>> support for the flexcan driver and clarify the documentation with
>> respect to error messages.
>>
>> regards, Marc
>>
>> ---
>>
>> The following changes since commit 31a67102f4762df5544bc2dfb34a931233d2a5b2:
>>
>>   Fix blocking allocations called very early during bootup (2012-05-21 12:52:42 -0700)
>>
>> are available in the git repository at:
>>   git@gitorious•org:linux-can/linux-can-next.git master
> 
> That should be:
> 
> git://gitorious.org/linux-can/linux-can-next.git master
> 
> Sorry for the noise,
> Marc
> 



  reply	other threads:[~2012-06-06 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03 22:52 pull-request: can-next 2012-06-04 Marc Kleine-Budde
2012-06-04 15:52 ` Marc Kleine-Budde
2012-06-06 18:02   ` Oliver Hartkopp [this message]
2012-06-06 18:15     ` David Miller
2012-06-06 21:57       ` Marc Kleine-Budde
2012-06-06 22:42         ` 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=4FCF9B3B.1070105@hartkopp.net \
    --to=socketcan@hartkopp$(echo .)net \
    --cc=davem@davemloft$(echo .)net \
    --cc=linux-can@vger$(echo .)kernel.org \
    --cc=mkl@pengutronix$(echo .)de \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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