From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Thu, 1 Jun 2017 11:57:48 -0400 Subject: [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2 In-Reply-To: <20170601155609.GA39518@eris.local> References: <20170509124341.GA5304@eris.local> <7ca52b2f-c0d8-5916-9330-7252c20e0097@suse.de> <20170601124503.GA37963@eris.local> <20170601125726.GJ10782@bill-the-cat> <20170601140448.GA38166@eris.local> <20170601155609.GA39518@eris.local> Message-ID: <20170601155748.GU10782@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de On Thu, Jun 01, 2017 at 05:56:09PM +0200, Patrick Wildt wrote: > On Thu, Jun 01, 2017 at 08:27:02PM +0530, Jagan Teki wrote: > > On Thu, Jun 1, 2017 at 8:23 PM, Andreas F=C3=A4rber = wrote: > > > Am 01.06.2017 um 16:04 schrieb Patrick Wildt: > > >> What's holding us up from using the Linux device trees without any > > >> changes? This diff I attach inline copies all a64, h3 and h5 related > > >> files from v4.12-rc3 (so, mainline) and modifies the emac driver to > > >> use the new pinmux attributes. > > > > > > Andre or someone had already sent a series sync'ing a64 and pine64. C= an > > > you keep h5/h3 separate or rebase onto that series please to not cause > > > merge conflicts? Thanks for your work on this. > >=20 > > Yeah, it's been on u-boot-sunxi/master > >=20 > > thanks! >=20 > I had already rebased it against u-boot-sunxi/master, so the attached > diff should be fine. Should I send it as a separate [PATCH] mail? To be clear, you were re-syncing those boards with only changes that will be going upstream to the Linux kernel at some point, right? Or are already there? And nothing U-Boot specific? --=20 Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: