From: Rob Herring <robherring2@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: "Vishwanathrao Badarkhe, Manish" <manishv.b@ti.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Landley <rob@landley.net>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gps6507x.txt: Remove executable bits
Date: Fri, 12 Jul 2013 17:06:39 -0500 [thread overview]
Message-ID: <51E07DEF.6030308@gmail.com> (raw)
In-Reply-To: <1373650307.2614.10.camel@joe-AO722>
On 07/12/2013 12:31 PM, Joe Perches wrote:
> Documentation shouldn't be executable.
>
> Signed-off-by: Joe Perches <joe@perches.com>
Acked-by: Rob Herring <rob.herring@calxeda.com>
> ---
> diff --git a/Documentation/devicetree/bindings/mfd/tps6507x.txt b/Documentation/devicetree/bindings/mfd/tps6507x.txt
> old mode 100755
> new mode 100644
>
>
prev parent reply other threads:[~2013-07-12 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 17:31 [PATCH] gps6507x.txt: Remove executable bits Joe Perches
2013-07-12 22:06 ` Rob Herring [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=51E07DEF.6030308@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishv.b@ti.com \
--cc=rob@landley.net \
/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).