From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND PATCH] arm: dts: am33xx: Remove redundant interrupt-parent property
Date: Thu, 10 Aug 2017 19:01:46 -0400 [thread overview]
Message-ID: <20170810230146.GE20467@bill-the-cat> (raw)
In-Reply-To: <1502359824-6915-1-git-send-email-sunil.m@techveda.org>
On Thu, Aug 10, 2017 at 03:40:24PM +0530, sunil.m at techveda.org wrote:
> From: Suniel Mahesh <sunil.m@techveda.org>
>
> Upstream Linux has the Interrupt-parent property being removed
> from mmc, mac, lcdc and tscadc sub nodes in the dtsi file.
> Interrupt-parent property is already defined in the root node.
> Therefore, update the dtsi to mimic this change and remove duplicates.
>
> Signed-off-by: Suniel Mahesh <sunil.m@techveda.org>
> ---
> Note:
> - Compile tested on latest u-boot mainline tree no build issues.
> - commit information upstream Linux:
> arm: dts: am33xx: Remove redundant interrupt-parent property
> sha1: de09eb52a1cceb6f80464a008c67c7bebb242314
Can you please re-sync with that commit ID for all am33xx DTS files and
mention it (or perhaps v4.13-rc3 or so) in the commit message? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170810/14ba18bb/attachment.sig>
next prev parent reply other threads:[~2017-08-10 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 10:10 [U-Boot] [RESEND PATCH] arm: dts: am33xx: Remove redundant interrupt-parent property sunil.m at techveda.org
2017-08-10 23:01 ` Tom Rini [this message]
2017-08-12 7:56 ` [U-Boot] [PATCH v2] arm: dts: am33xx: sync DTS with Linux 4.13-rc4 sunil.m at techveda.org
2017-08-13 21:20 ` Tom Rini
2017-08-26 20:45 ` [U-Boot] [U-Boot, " Tom Rini
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=20170810230146.GE20467@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox