From: Andy Gross <andy.gross@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: Riku Voipio <riku.voipio@linaro.org>,
Rob Clark <robdclark@gmail.com>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
David Brown <david.brown@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Rename SBC to DragonBoard 410c
Date: Thu, 5 Oct 2017 23:41:10 -0500 [thread overview]
Message-ID: <20171006044110.GA3105@hector> (raw)
In-Reply-To: <3241c0f0-cc40-0262-a771-a0b6fd020b54@suse.de>
On Thu, Oct 05, 2017 at 03:06:34PM +0200, Alexander Graf wrote:
<snip>
> You could also simply carry around both, with for example the dragonboard
> one including sbc and overriding the machine name.
>
> But please don't remove any device tree file names that were there before.
> It only causes confusion for everyone.
This seems to be a reasonable solution.
Regards,
Andy
next prev parent reply other threads:[~2017-10-06 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 9:11 [PATCH 1/2] arm64: qcom: sbc: Name GPIO lines Linus Walleij
2017-10-03 9:11 ` [PATCH 2/2] arm64: dts: qcom: Rename SBC to DragonBoard 410c Linus Walleij
2017-10-03 12:25 ` Srinivas Kandagatla
2017-10-03 16:37 ` Rob Clark
2017-10-03 17:49 ` Nicolas Dechesne
2017-10-03 18:54 ` Rob Clark
2017-10-04 21:23 ` Rob Clark
2017-10-04 22:09 ` Stephen Boyd
2017-10-04 22:12 ` Rob Clark
2017-10-04 23:21 ` Stephen Boyd
2017-10-04 23:49 ` Rob Clark
2017-10-05 12:54 ` Riku Voipio
2017-10-05 13:06 ` Alexander Graf
2017-10-06 4:41 ` Andy Gross [this message]
2017-10-03 20:58 ` Bjorn Andersson
2017-10-04 21:45 ` [PATCH 1/2] arm64: qcom: sbc: Name GPIO lines Stephen Boyd
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=20171006044110.GA3105@hector \
--to=andy.gross@linaro.org \
--cc=agraf@suse.de \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=nicolas.dechesne@linaro.org \
--cc=riku.voipio@linaro.org \
--cc=robdclark@gmail.com \
--cc=sboyd@codeaurora.org \
--cc=srinivas.kandagatla@linaro.org \
/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).