From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/4] can: Allwinner A10/A20 CAN Controller support - Summary
Date: Thu, 17 Sep 2015 20:27:37 +0200 [thread overview]
Message-ID: <20150917182737.GK4684@lukather> (raw)
In-Reply-To: <55FB028F.7070206@hartkopp.net>
On Thu, Sep 17, 2015 at 08:12:31PM +0200, Oliver Hartkopp wrote:
>
>
> 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.
Hmmm, actually, I meant 2 and 3, the two defconfig patches.
The driver and bindings should of course go through Marc's tree.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150917/a7dd44e1/attachment.sig>
next prev parent reply other threads:[~2015-09-17 18:27 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 [this message]
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=20150917182737.GK4684@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).