netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, kernel@pengutronix.de, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2017-12-01,Re: pull-request: can-nexto 2017-12-01,Re: pull-request: can-next 2017-12-01,Re: pull-request: can-next 2017-12-01
Date: Mon, 15 Jan 2018 16:14:33 -0500 (EST)	[thread overview]
Message-ID: <20180115.161433.1583031609797218068.davem@davemloft.net> (raw)
In-Reply-To: <2372427e-2db4-b386-f51d-86f976033765@pengutronix.de>

From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Mon, 15 Jan 2018 21:54:29 +0100

> On 01/15/2018 06:55 PM, David Miller wrote:
>> From: Marc Kleine-Budde <mkl@pengutronix.de>
>> Date: Mon, 15 Jan 2018 14:02:23 +0100
>> 
>>> Hello David,
>>>
>>>
>>> On 01/05/2018 12:08 PM, Marc Kleine-Budde wrote:
>>>> Hello David,
>>>>
>>>> this is a pull request of 7 patches for net-next/master.
>>>>
>>>> All patches are by me. Patch 6 is for the "can_raw" protocol and add
>>>> error checking to the bind() function. All other patches clean up the
>>>> coding style and remove unused parameters in various CAN drivers and
>>>> infrastructure.
>>>
>>> this pull request is still open. Any objections to pull this?
>> 
>> You gave me an SSH URL:
>> 
>> 	ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.16-20180105
>> 
>> Or did you plan to give my your SSH password so that I can pull this? :-)
>> 
>> Please resubmit with a proper git:// URL I can actually pull from.
> 
> I don't see a reason, why you need my ssh keys. That was intentional.
> 
> As long as you have your SSH keys, you have read only access to my (and
> the git repos of the other kernel developers) on git.kernel.org. I'm
> already fetching from net and net-next via ssh:

Ok, I didn't know this.

Pulled, thanks.

      reply	other threads:[~2018-01-15 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 11:08 pull-request: can-next 2017-12-01 Marc Kleine-Budde
2018-01-15 13:02 ` Marc Kleine-Budde
2018-01-15 17:55   ` pull-request: can-next 2017-12-01,Re: " David Miller
2018-01-15 20:54     ` Marc Kleine-Budde
2018-01-15 21:14       ` 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=20180115.161433.1583031609797218068.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=kernel@pengutronix.de \
    --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).