linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Thierry Reding
	<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Alexandre Courbot
	<gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ARM: tegra: use generated pinmux for Beaver board
Date: Mon, 02 Mar 2015 20:16:09 +0100	[thread overview]
Message-ID: <1425323769.2182.0.camel@lynxeye.de> (raw)
In-Reply-To: <1420591830.25483.16.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>

Am Mittwoch, den 07.01.2015, 01:50 +0100 schrieb Lucas Stach:
> Am Montag, den 05.01.2015, 15:08 -0700 schrieb Stephen Warren:
> > On 01/05/2015 02:57 PM, Lucas Stach wrote:
> > > Replace the current incomplete pinmux setup with a proper one generated
> > > using the tegra pinmux scripts.
> > 
> > I assume this is identical to the existing content, it's just that the 
> > node sort order changed to match the auto-generation order?
> > 
> Yes auto-generation changes the representation of the nodes a bit, but I
> made sure to keep the properties of the existing kernel DT pinmux where
> they were different from the U-Boot pinmux.
> 
> > If so,
> > Acked-by: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
> 
This has not been applied. Could anyone please pick this up, so it
doesn't miss yet another merge window?

Thanks,
Lucas

  parent reply	other threads:[~2015-03-02 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 21:57 [PATCH] ARM: tegra: use generated pinmux for Beaver board Lucas Stach
2015-01-05 22:08 ` Stephen Warren
     [not found]   ` <54AB0B68.7050704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-01-07  0:50     ` Lucas Stach
     [not found]       ` <1420591830.25483.16.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-02 19:16         ` Lucas Stach [this message]
     [not found]           ` <1425323769.2182.0.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-19 19:52             ` Lucas Stach
     [not found]               ` <1426794762.2212.0.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-23  8:59                 ` Thierry Reding

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=1425323769.2182.0.camel@lynxeye.de \
    --to=dev-8ppwabl0hbeelga04laivw@public.gmane.org \
    --cc=gnurou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    --cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).