From: Grant Likely <grant.likely@secretlab.ca>
To: Jason Cooper <jason@lakedaemon.net>
Cc: linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, Andrew Lunn <andrew@lunn.ch>,
Simon Guinot <simon.guinot@sequanux.org>
Subject: Re: [PATCH] devicetree: Move NS2 LEDs binding into LEDs directory
Date: Fri, 08 Feb 2013 22:05:41 +0000 [thread overview]
Message-ID: <20130208220541.5DDDD3E2C27@localhost> (raw)
In-Reply-To: <20130207132118.GE14746@titan.lakedaemon.net>
On Thu, 7 Feb 2013 08:21:18 -0500, Jason Cooper <jason@lakedaemon.net> wrote:
> On Thu, Feb 07, 2013 at 12:22:56PM +0000, Grant Likely wrote:
> > leds-ns2.txt is a binding for LEDs, not GPIOs. Move the documentation in
> > with the rest of the LEDs bindings.
> >
> > Cc: Andrew Lunn <andrew@lunn.ch>
> > Cc: Simon Guinot <simon.guinot@sequanux.org>
> > Cc: Jason Cooper <jason@lakedaemon.net>
> > Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> > ---
> > .../devicetree/bindings/gpio/leds-ns2.txt | 26 --------------------
> > .../devicetree/bindings/leds/leds-ns2.txt | 26 ++++++++++++++++++++
> > 2 files changed, 26 insertions(+), 26 deletions(-)
> > delete mode 100644 Documentation/devicetree/bindings/gpio/leds-ns2.txt
> > create mode 100644 Documentation/devicetree/bindings/leds/leds-ns2.txt
>
> Acked-by: Jason Cooper <jason@lakedaemon.net>
>
> or, if you want, I can queue it up. Just let me know.
No, I got it. It was trivial so I committed it directly without waiting
for review comments.
g.
prev parent reply other threads:[~2013-02-08 22:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 12:22 [PATCH] devicetree: Move NS2 LEDs binding into LEDs directory Grant Likely
2013-02-07 12:22 ` Grant Likely
[not found] ` <1360239776-14889-1-git-send-email-grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
2013-02-07 13:21 ` Jason Cooper
2013-02-07 13:21 ` Jason Cooper
2013-02-08 22:05 ` Grant Likely [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=20130208220541.5DDDD3E2C27@localhost \
--to=grant.likely@secretlab.ca \
--cc=andrew@lunn.ch \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=simon.guinot@sequanux.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.