From: Scott Branden <scott.branden@broadcom.com>
To: Eric Anholt <eric@anholt.net>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Stefan Wahren <stefan.wahren@i2se.com>
Cc: BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: move rpi into rpi directory
Date: Wed, 19 Jul 2017 13:25:51 -0700 [thread overview]
Message-ID: <ff694220-b771-4702-c9dc-536a3c87770e@broadcom.com> (raw)
In-Reply-To: <87mv80dvpo.fsf@eliezer.anholt.net>
Hi Eric,
On 17-07-19 01:21 PM, Eric Anholt wrote:
> Scott Branden <scott.branden@broadcom.com> writes:
>
>> Place rpi into its own subdirectory. This helps as the number
>> of Broadcom boards grow and we can separate them per SoC.
> It seems like pretty unnecessary churn to me, though I wouldn't
> necessarily block it. However, it conflicts with the patch I was
> preparing yesterday to try to resolve our DT merging troubles
> (https://lkml.org/lkml/2017/5/16/707), so I'd like to hold off on it for
> now.
I'm quite fine with dropping the rpi dts patch. I'm going to proceed
with the northstar2 patch
before more SoC and boards are introduced.
Thanks,
Scott
next prev parent reply other threads:[~2017-07-19 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 17:05 [PATCH 0/2] arm64: dts: cleanup Broadcom boards per SoC Scott Branden
2017-07-19 17:05 ` [PATCH 1/2] arm64: dts: move ns2 into northstar2 directory Scott Branden
2017-07-28 23:31 ` Florian Fainelli
2017-07-19 17:05 ` [PATCH 2/2] arm64: dts: move rpi into rpi directory Scott Branden
2017-07-19 20:21 ` Eric Anholt
2017-07-19 20:25 ` Scott Branden [this message]
2017-08-08 22:39 ` kbuild test robot
2017-07-28 14:39 ` [PATCH 0/2] arm64: dts: cleanup Broadcom boards per SoC Scott Branden
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=ff694220-b771-4702-c9dc-536a3c87770e@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®