[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c2911d7-f753-4d9f-b8d8-3bf011d58e52@TX2EHSMHS014.ehs.local>
Date: Mon, 29 Oct 2012 07:24:16 +0000
From: Michal Simek <michal.simek@...inx.com>
To: Josh Cartwright <josh.cartwright@...com>,
"arm@...nel.org" <arm@...nel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
John Linn <linnj@...inx.com>,
Nick Bowler <nbowler@...iptictech.com>,
Arnd Bergmann <arnd@...db.de>
Subject: RE: [PATCH v4 0/5] zynq subarch cleanups
Hi Josh,
Michal-
>
> Here is a v5 of the zynq cleanup patchset that addresses your feedback. I've
> intentionally left patches 4 and 5 in the set until we figure out the appropriate
> way to get them in tree (feel free to just apply 1-3)
I am ok to pick just several patches from your patchset. But this is no definitely
good working style. Not expert for submission process but I think that
if there is one broken patch maintainer shouldn't apply it.
Can someone else check this?
> I've also moved the uart mapping in patch 5 to a known working address, until
> we can work out what is happening there. This should allow this patchset to be
> applied and have the zc702 boot.
Will look at it and apply if works.
> You had suggested removing/renaming the zynq-ep107.dts; it wasn't clear
> whether you had wanted that in this patchset or not. I'm going to assume not.
> I'll follow up with this, after this patchset is applied, if that works for you.
Not in this patchset. Sure feel free to send it.
Thanks,
Michal
--
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