From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@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, 23 Mar 2015 09:59:59 +0100 [thread overview]
Message-ID: <20150323085958.GA11268@ulmo> (raw)
In-Reply-To: <1426794762.2212.0.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
On Thu, Mar 19, 2015 at 08:52:42PM +0100, Lucas Stach wrote:
> Am Montag, den 02.03.2015, 20:16 +0100 schrieb Lucas Stach:
> > 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?
> >
> Friendly ping.
Applied, thanks.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: use generated pinmux for Beaver board
Date: Mon, 23 Mar 2015 09:59:59 +0100 [thread overview]
Message-ID: <20150323085958.GA11268@ulmo> (raw)
In-Reply-To: <1426794762.2212.0.camel@lynxeye.de>
On Thu, Mar 19, 2015 at 08:52:42PM +0100, Lucas Stach wrote:
> Am Montag, den 02.03.2015, 20:16 +0100 schrieb Lucas Stach:
> > 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@nvidia.com>
> > >
> > This has not been applied. Could anyone please pick this up, so it
> > doesn't miss yet another merge window?
> >
> Friendly ping.
Applied, thanks.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150323/852d9787/attachment.sig>
next prev parent reply other threads:[~2015-03-23 8:59 UTC|newest]
Thread overview: 12+ 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 21:57 ` Lucas Stach
2015-01-05 22:08 ` Stephen Warren
2015-01-05 22:08 ` Stephen Warren
[not found] ` <54AB0B68.7050704-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2015-01-07 0:50 ` Lucas Stach
2015-01-07 0:50 ` Lucas Stach
[not found] ` <1420591830.25483.16.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-02 19:16 ` Lucas Stach
2015-03-02 19:16 ` Lucas Stach
[not found] ` <1425323769.2182.0.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-19 19:52 ` Lucas Stach
2015-03-19 19:52 ` Lucas Stach
[not found] ` <1426794762.2212.0.camel-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2015-03-23 8:59 ` Thierry Reding [this message]
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=20150323085958.GA11268@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=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 \
/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.