U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Wildt <patrick@blueri.se>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: sunxi: initial support for NanoPi Neo2
Date: Thu, 1 Jun 2017 17:56:09 +0200	[thread overview]
Message-ID: <20170601155609.GA39518@eris.local> (raw)
In-Reply-To: <CAD6G_RR0rrjhqT7T-=6SJQ7c5Uv1wdbCaVvnzcGaKbprok8DvA@mail.gmail.com>

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!
> -- 
> Jagan Teki
> Free Software Engineer | www.openedev.com
> U-Boot, Linux | Upstream Maintainer
> Hyderabad, India.

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?

Thanks,
Patrick

  reply	other threads:[~2017-06-01 15:56 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 [this message]
2017-06-01 15:57                 ` Tom Rini
2017-06-01 15:59                   ` Patrick Wildt
2017-06-01 16:03                     ` Tom Rini

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=20170601155609.GA39518@eris.local \
    --to=patrick@blueri.se \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox