From: Linus Walleij <linus.walleij@linaro.org>
To: Rob Herring <robh@kernel.org>
Cc: Wolfram Sang <wsa@the-dreams.de>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Sebastian Reichel <sre@kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] Documentation: power: reset: move gpio-{poweroff|restart} to proper place
Date: Tue, 19 Apr 2016 10:19:38 +0200 [thread overview]
Message-ID: <CACRpkdZKS77CQpf5xQ4aA++jg6SH32BptoSbDCg0yugF4O0Jtw@mail.gmail.com> (raw)
In-Reply-To: <CAL_JsqKK1QmGdyae-P9SoP2-7JiLK1XCyskxbd-wrn+7CidMJw@mail.gmail.com>
On Fri, Apr 15, 2016 at 6:53 PM, Rob Herring <robh@kernel.org> wrote:
> On Fri, Apr 15, 2016 at 2:48 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>> On Tue, Apr 12, 2016 at 6:00 PM, Wolfram Sang <wsa@the-dreams.de> wrote:
>>
>>> From: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>>
>>> I did only find them after a fuzzy search, so let them be where one
>>> would expect them.
>>>
>>> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
>>
>> I saw this the other day too I agree.
>> Sebastian: are you OK that I move this by committing the patch to the GPIO tree?
>> DT maintainers: OK?
>
> Acked-by: Rob Herring <robh@kernel.org>
>
> Seems like this should go thru my tree though, but I don't have the patch.
I have it merged in my tree, is is OK or shall I extract it and send
it to you?
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-04-19 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 16:00 [PATCH] Documentation: power: reset: move gpio-{poweroff|restart} to proper place Wolfram Sang
2016-04-15 7:48 ` Linus Walleij
2016-04-15 13:27 ` Sebastian Reichel
2016-04-15 16:53 ` Rob Herring
2016-04-19 8:19 ` Linus Walleij [this message]
2016-04-15 14:05 ` Linus Walleij
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=CACRpkdZKS77CQpf5xQ4aA++jg6SH32BptoSbDCg0yugF4O0Jtw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=wsa@the-dreams.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 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.