From: Tony Lindgren <tony@atomide.com>
To: Neeraj Dantu <dantuguf14105@gmail.com>
Cc: devicetree@vger.kernel.org, Jason Kridner <jkridner@gmail.com>,
Neeraj Dantu <neeraj.dantu@octavosystems.com>,
linux-omap@vger.kernel.org,
Robert Nelson <robertcnelson@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Fix file permission for am335x-osd3358-sm-red.dts
Date: Tue, 28 Aug 2018 08:53:51 -0700 [thread overview]
Message-ID: <20180828155351.GN7523@atomide.com> (raw)
In-Reply-To: <20180828153816.1152-1-neeraj.dantu@octavosystems.com>
* Neeraj Dantu <dantuguf14105@gmail.com> [180828 15:42]:
> OSD3358-SM-RED is a dev board for OSD335x System-in-Package(SiP) devices from
> Octavo Systems.
>
> This board family can be indentified by the A335BNLTOS00 in the at24 eeprom:
> A2: [aa 55 33 ee 41 33 33 35 42 4e 4c 54 4f 53 30 30 |.U3.A335BNLTOS00|]
>
> https://octavosystems.com/octavo_products/osd3358-sm-red/
Hmm can you please repost with a correct patch description?
Something along the lines of:
Fix wrong mode for dts file added by commit bb3e3fbbac86
("ARM: dts: Add DT support for Octavo Systems OSD3358-SM-RED
based on TI AM335x").
Regards,
Tony
> Signed-off-by: Neeraj Dantu <neeraj.dantu@octavosystems.com>
> CC: Tony Lindgren <tony@atomide.com>
> CC: Robert Nelson <robertcnelson@gmail.com>
> CC: Jason Kridner <jkridner@gmail.com>
> ---
> Changes:
> - Fix file permission
> ---
> arch/arm/boot/dts/am335x-osd3358-sm-red.dts | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> mode change 100755 => 100644 arch/arm/boot/dts/am335x-osd3358-sm-red.dts
>
> diff --git a/arch/arm/boot/dts/am335x-osd3358-sm-red.dts b/arch/arm/boot/dts/am335x-osd3358-sm-red.dts
> old mode 100755
> new mode 100644
> --
> 2.7.4
>
prev parent reply other threads:[~2018-08-28 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 15:38 [PATCH] Fix file permission for am335x-osd3358-sm-red.dts Neeraj Dantu
2018-08-28 15:53 ` Tony Lindgren [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=20180828155351.GN7523@atomide.com \
--to=tony@atomide.com \
--cc=dantuguf14105@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=neeraj.dantu@octavosystems.com \
--cc=robertcnelson@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).