From: Sekhar Nori <nsekhar@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Robert Nelson <robertcnelson@gmail.com>,
Nishanth Menon <nm@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux kernel <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>,
Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1
Date: Wed, 7 Sep 2016 10:39:26 +0530 [thread overview]
Message-ID: <dc4ed90a-223d-69c0-d350-39b6a9d5ce6f@ti.com> (raw)
In-Reply-To: <20160906200553.wqkvwsfww3rllhd5@atomide.com>
On Wednesday 07 September 2016 01:35 AM, Tony Lindgren wrote:
> And the am335x shared dtsi files are not enough. It's silly how many
> times we're duplicating the same things over and over again for USB
> setup for various am335x boards for example.
>
> So my take is that we need more shared dtsi files, not less.
Alright, thanks for weighing in, Tony.
Regards,
Sekhar
next prev parent reply other threads:[~2016-09-07 5:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 9:05 [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
2016-09-02 9:05 ` [PATCH 1/2] ARM: dts: am57xx-beagle-x15: Remove pinmux configurations Nishanth Menon
2016-09-02 10:18 ` Sekhar Nori
2016-09-02 14:52 ` Nishanth Menon
2016-09-02 9:06 ` [PATCH 2/2] ARM: dts: am57xx-beagle-x15: Add support for rev B1 Nishanth Menon
2016-09-02 9:58 ` Tomi Valkeinen
2016-09-02 10:01 ` Nishanth Menon
2016-09-02 11:48 ` Tomi Valkeinen
2016-09-02 10:41 ` Sekhar Nori
2016-09-02 11:18 ` Tomi Valkeinen
2016-09-02 13:52 ` Robert Nelson
2016-09-02 15:01 ` Nishanth Menon
2016-09-02 15:06 ` Tony Lindgren
2016-09-06 10:10 ` Sekhar Nori
2016-09-06 20:05 ` Tony Lindgren
2016-09-07 5:09 ` Sekhar Nori [this message]
2016-09-02 9:14 ` [PATCH 0/2] ARM: dts: Introduce support for rev BeagleBoard-X15 B1 Nishanth Menon
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=dc4ed90a-223d-69c0-d350-39b6a9d5ce6f@ti.com \
--to=nsekhar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@beagleboard.org \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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).