All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2
Date: Thu, 1 Jun 2017 12:03:40 -0400	[thread overview]
Message-ID: <20170601160340.GV10782@bill-the-cat> (raw)
In-Reply-To: <20170601155934.GB39518@eris.local>

On Thu, Jun 01, 2017 at 05:59:35PM +0200, Patrick Wildt wrote:
> On Thu, Jun 01, 2017 at 11:57:48AM -0400, Tom Rini wrote:
> > 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ärber <afaerber@suse.de> 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. Can
> > > > > you keep h5/h3 separate or rebase onto that series please to not cause
> > > > > merge conflicts? Thanks for your work on this.
> > > > 
> > > > Yeah, it's been on u-boot-sunxi/master
> > > > 
> > > > thanks!
> > > 
> > > 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?
> 
> More the other way around.  I replaced the u-boot ones with the files
> from linux, so there should be nothing u-boot specific anymore if there
> was at all.  Is that approach incorrect?

No, that's what I wanted to hear, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170601/c4b7a636/attachment.sig>

      reply	other threads:[~2017-06-01 16:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 12:43 [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2 Patrick Wildt
2017-05-09 13:13 ` Tom Rini
2017-05-24 11:50 ` Andreas Färber
2017-05-24 12:44   ` Andre Przywara
2017-05-24 12:52     ` Tom Rini
2017-05-24 14:27     ` Andreas Färber
2017-06-01 12:45     ` Patrick Wildt
2017-06-01 12:57       ` Tom Rini
2017-06-01 14:04         ` Patrick Wildt
2017-06-01 14:53           ` Andreas Färber
2017-06-01 14:57             ` Jagan Teki
2017-06-01 15:56               ` Patrick Wildt
2017-06-01 15:57                 ` Tom Rini
2017-06-01 15:59                   ` Patrick Wildt
2017-06-01 16:03                     ` Tom Rini [this message]

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=20170601160340.GV10782@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.