From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Gerhard Bertelsmann <info@gerhard-bertelsmann.de>,
wg@grandegger.com, mkl@pengutronix.de, linux-can@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary
Date: Thu, 17 Sep 2015 20:29:51 +0200 [thread overview]
Message-ID: <55FB069F.8040804@hartkopp.net> (raw)
In-Reply-To: <20150917182737.GK4684@lukather>
Hi Maxime,
On 17.09.2015 20:27, Maxime Ripard wrote:
> On Thu, Sep 17, 2015 at 08:12:31PM +0200, Oliver Hartkopp wrote:
>> New CAN drivers go via can-next and net-next into mainline.
>>
>
> Hmmm, actually, I meant 2 and 3, the two defconfig patches.
>
> The driver and bindings should of course go through Marc's tree.
Ok. Thanks for the fix :-)
Regards,
Oliver
next prev parent reply other threads:[~2015-09-17 18:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 11:21 [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 1/3] can: Allwinner A10/A20 CAN Controller support - Devicetree bindings Gerhard Bertelsmann
2015-09-17 8:04 ` Marc Kleine-Budde
2015-09-17 10:06 ` Maxime Ripard
2015-09-17 10:05 ` Maxime Ripard
2015-09-16 11:21 ` [PATCH v8 2/4] can: Allwinner A10/A20 CAN Controller support - Defconfig Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 3/4] " Gerhard Bertelsmann
2015-09-16 11:21 ` [PATCH v8 4/4] can: Allwinner A10/A20 CAN Controller support - Kernel module Gerhard Bertelsmann
2015-09-17 17:52 ` Maxime Ripard
2015-09-17 17:54 ` [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary Maxime Ripard
2015-09-17 18:12 ` Oliver Hartkopp
2015-09-17 18:27 ` Maxime Ripard
2015-09-17 18:29 ` Oliver Hartkopp [this message]
2015-09-17 20:57 ` Marc Kleine-Budde
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=55FB069F.8040804@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=info@gerhard-bertelsmann.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=wg@grandegger.com \
/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).