From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
Gerhard Bertelsmann <info@gerhard-bertelsmann.de>
Cc: 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:12:31 +0200 [thread overview]
Message-ID: <55FB028F.7070206@hartkopp.net> (raw)
In-Reply-To: <20150917175444.GJ4684@lukather>
On 17.09.2015 19:54, Maxime Ripard wrote:
> On Wed, Sep 16, 2015 at 01:21:18PM +0200, Gerhard Bertelsmann wrote:
>> Hi,
>>
>> please find attached the next version of my patch set. I have
>> taken all remarks from Maxime Ripard into the new version
>>
>> Please review, test and report bugs if exists.
>>
>> The patchset applies to all recent Kernel versions (4.x, next etc.).
>>
>> [PATCH v8 1/4] Device Tree Binding Documentation
>> [PATCH v8 2/4] Defconfig multi_v7
>> [PATCH v8 3/4] Defconfig sunxi
>> [PATCH v8 4/4] Kernel Module
>
> Applied 3 and 4.
Applied to what tree?
That's not the friendly way when Marc asks you about the documentation about
the device tree (patch 1) and you commit the CAN driver and the sunxi
defconfig (patch 3 & 4) that he mainly reviewed to whatever tree.
New CAN drivers go via can-next and net-next into mainline.
So please answer Marcs question and let him queue up the CAN driver via
can-next himself.
Thanks,
Oliver
next prev parent reply other threads:[~2015-09-17 18:12 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 [this message]
2015-09-17 18:27 ` Maxime Ripard
2015-09-17 18:29 ` Oliver Hartkopp
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=55FB028F.7070206@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).