From: Joe Perches <joe@perches.com>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: Rob Herring <robherring2@gmail.com>,
"arm@kernel.org" <arm@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [trivial PATCH] arm: dts: socfpga: Remove executable permission bits
Date: Mon, 20 Apr 2015 08:45:04 -0700 [thread overview]
Message-ID: <1429544704.4216.39.camel@perches.com> (raw)
In-Reply-To: <CADhT+wf4UY+N+k9BLk5WcGd5czjo8CK86ocDoCPMDVjzLGay2w@mail.gmail.com>
On Mon, 2015-04-20 at 10:37 -0500, Dinh Nguyen wrote:
> On Thu, Apr 16, 2015 at 5:54 PM, Rob Herring <robherring2@gmail.com> wrote:
> > +arm-soc
> > On Thu, Apr 16, 2015 at 5:49 PM, Joe Perches <joe@perches.com> wrote:
> >> Change the .dts file permissions from 755 to 644.
> >> Signed-off-by: Joe Perches <joe@perches.com>
> > ARM dts files go in thru arm-soc tree.
> > Acked-by: Rob Herring <robh@kernel.org>
> Thanks for doing this, but this patch:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/335418.html
> should address the same issue.
That's fine with me.
This patch is not in -next yet though.
Is someone going to apply/push/pull it?
next prev parent reply other threads:[~2015-04-20 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 22:49 [trivial PATCH] arm: dts: socfpga: Remove executable permission bits Joe Perches
[not found] ` <1429224565.2850.62.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-04-16 22:54 ` Rob Herring
[not found] ` <CAL_Jsq+VN15c-LE_iQzx1AnoPWmNEtjVgiEBb2OkHQPP=ZrQMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-20 15:37 ` Dinh Nguyen
2015-04-20 15:45 ` Joe Perches [this message]
2015-04-20 18:58 ` Dinh Nguyen
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=1429544704.4216.39.camel@perches.com \
--to=joe@perches.com \
--cc=arm@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
/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).