netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: David Miller <davem@davemloft.net>
Cc: socketcan@hartkopp.net, netdev@vger.kernel.org,
	linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2012-06-04
Date: Wed, 06 Jun 2012 23:57:10 +0200	[thread overview]
Message-ID: <4FCFD236.8010002@pengutronix.de> (raw)
In-Reply-To: <20120606.111538.2166268452793199990.davem@davemloft.net>

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

On 06/06/2012 08:15 PM, David Miller wrote:
> From: Oliver Hartkopp <socketcan@hartkopp.net>
> Date: Wed, 06 Jun 2012 20:02:35 +0200
> 
>> 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
> 
> Strange, I thought I had pulled it, I've done so now, thanks.

Thanks.

I've some patches for net-next which depend on net. When do you merge
net to net-next?

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: 262 bytes --]

  reply	other threads:[~2012-06-06 21:57 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
2012-06-06 18:15     ` David Miller
2012-06-06 21:57       ` Marc Kleine-Budde [this message]
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=4FCFD236.8010002@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=davem@davemloft.net \
    --cc=linux-can@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    /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).