[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55FB028F.7070206@hartkopp.net>
Date: Thu, 17 Sep 2015 20:12:31 +0200
From: Oliver Hartkopp <socketcan@...tkopp.net>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>,
Gerhard Bertelsmann <info@...hard-bertelsmann.de>
CC: wg@...ndegger.com, mkl@...gutronix.de, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support
- Summary
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists