From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Eric Brower <ebrower-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 1/1] ARM: DT: tegra: Add gpio-leds to Tegra30 Beaver
Date: Fri, 17 May 2013 17:52:29 -0600 [thread overview]
Message-ID: <5196C2BD.4040709@wwwdotorg.org> (raw)
In-Reply-To: <1368232829-25716-1-git-send-email-ebrower-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
On 05/10/2013 06:40 PM, Eric Brower wrote:
> Add support for general-purpose LEDs present on Beaver
I've applied this to Tegra's for-3.11/dt branch. When applying, I moved
the newly added node to maintain the node sort order.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: DT: tegra: Add gpio-leds to Tegra30 Beaver
Date: Fri, 17 May 2013 17:52:29 -0600 [thread overview]
Message-ID: <5196C2BD.4040709@wwwdotorg.org> (raw)
In-Reply-To: <1368232829-25716-1-git-send-email-ebrower@nvidia.com>
On 05/10/2013 06:40 PM, Eric Brower wrote:
> Add support for general-purpose LEDs present on Beaver
I've applied this to Tegra's for-3.11/dt branch. When applying, I moved
the newly added node to maintain the node sort order.
next prev parent reply other threads:[~2013-05-17 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 0:40 [PATCH 1/1] ARM: DT: tegra: Add gpio-leds to Tegra30 Beaver Eric Brower
2013-05-11 0:40 ` Eric Brower
[not found] ` <1368232829-25716-1-git-send-email-ebrower-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-05-17 23:52 ` Stephen Warren [this message]
2013-05-17 23:52 ` Stephen Warren
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=5196C2BD.4040709@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=ebrower-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@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.