From: Baruch Siach <baruch@tkos.co.il>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/8] ARM: Conexant Digicolor CX92755 SoC support
Date: Sun, 11 Jan 2015 13:33:27 +0200 [thread overview]
Message-ID: <20150111113327.GQ2481@sapphire.tkos.co.il> (raw)
In-Reply-To: <5966468.GiJYdzCvnt@wuerfel>
Hi Arnd,
On Thu, Jan 08, 2015 at 11:46:46PM +0100, Arnd Bergmann wrote:
> On Thursday 08 January 2015 21:39:56 Baruch Siach wrote:
> > This series adds initial support for the Conexant CX92755 SoC. The CX92755 is
> > one of the Digicolor series of SoCs, all sharing many of the same peripherals.
> > The code was tested on the CX92755 evaluation kit, AKA Equinox.
> >
> > Uses attempting to try this code will most likely also want the UART/console
> > driver available from https://patchwork.kernel.org/patch/5515861/.
>
> Looks great overall now.
>
> I have just two more comments in one patch, and one general request:
>
> Please add a patch description for every patch. The text above would
> be a good start for the first patch, but it would be lost in the git
> history if it's only in the cover letter.
>
> other than that, feel free to add my
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
Thanks.
> Once there are no more review comments, please submit the first three
> patches to arm@kernel.org, and send the other patches as separate
> series to the respective maintainers for irqchip and clocksource.
What about the last patch in this series (ARM: devicetree: document supported
Conexant Digicolor SoC)? What tree should it go through.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-01-11 11:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 19:39 Baruch Siach
2015-01-08 19:39 ` [PATCH v2 1/8] ARM: initial support for Conexant Digicolor CX92755 SoC Baruch Siach
2015-01-08 19:39 ` [PATCH v2 2/8] ARM: digicolor: add low level debug support Baruch Siach
2015-01-08 19:39 ` [PATCH v2 3/8] ARM: digicolor: add minimal device tree description Baruch Siach
2015-01-08 22:41 ` Arnd Bergmann
2015-01-09 11:46 ` Mark Rutland
2015-01-11 9:38 ` Baruch Siach
2015-01-08 19:40 ` [PATCH v2 4/8] irqchip: devicetree: document Conexant Digicolor irq binding Baruch Siach
2015-01-09 11:50 ` Mark Rutland
2015-01-11 11:21 ` Baruch Siach
2015-01-09 15:12 ` Sergei Shtylyov
2015-01-11 11:29 ` Baruch Siach
2015-01-08 19:40 ` [PATCH v2 5/8] irqchip: Conexant CX92755 interrupts controller driver Baruch Siach
2015-01-08 19:40 ` [PATCH v2 6/8] clocksource: devicetree: document Conexant Digicolor timer binding Baruch Siach
2015-01-08 19:40 ` [PATCH v2 7/8] clocksource: driver for Conexant Digicolor SoC timer Baruch Siach
2015-01-08 19:40 ` [PATCH v2 8/8] ARM: devicetree: document supported Conexant Digicolor SoC Baruch Siach
2015-01-08 22:46 ` [PATCH v2 0/8] ARM: Conexant Digicolor CX92755 SoC support Arnd Bergmann
2015-01-11 11:33 ` Baruch Siach [this message]
2015-01-11 15:49 ` Arnd Bergmann
2015-01-28 22:33 ` Paul Bolle
2015-01-28 22:41 ` Baruch Siach
2015-01-28 22:52 ` Paul Bolle
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=20150111113327.GQ2481@sapphire.tkos.co.il \
--to=baruch@tkos.co.il \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®