From: Linus Walleij <linus.walleij@linaro.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Ruben Ayrapetyan <ruben.ayrapetyan@arm.com>,
Kevin Brodsky <kevin.brodsky@arm.com>,
Liviu Dudau <liviu.dudau@arm.com>,
"open list:DRM PANEL DRIVERS" <dri-devel@lists.freedesktop.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Brian Starkey <brian.starkey@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] arm64: dts: fast models: Increase clcd's max-memory-bandwidth
Date: Mon, 5 Aug 2019 12:18:06 +0200 [thread overview]
Message-ID: <CACRpkdbPhxW2-vDhPDz-KpD-AxPJL+Px_ZH8cWVVbCiYpJh3PA@mail.gmail.com> (raw)
In-Reply-To: <042d5c3d-96fe-5466-3869-a0a3a08b964d@arm.com>
On Thu, Jul 25, 2019 at 5:15 PM Robin Murphy <robin.murphy@arm.com> wrote:
> Given that the property is optional anyway, would it hurt to just remove
> it? After trying to dig up any relevant internal email history, it's
> still far from clear how and why it got here in the first place.
Isn't it just my sloppy copy-paste when fixing up the device trees
for the DRM transition? I agree it should just be removed.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-05 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 14:50 [PATCH] arm64: dts: fast models: Increase clcd's max-memory-bandwidth Kevin Brodsky
2019-07-25 15:15 ` Robin Murphy
2019-07-25 16:58 ` Kevin Brodsky
2019-08-05 10:18 ` Linus Walleij [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=CACRpkdbPhxW2-vDhPDz-KpD-AxPJL+Px_ZH8cWVVbCiYpJh3PA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=brian.starkey@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=pawel.moll@arm.com \
--cc=robin.murphy@arm.com \
--cc=ruben.ayrapetyan@arm.com \
--cc=sudeep.holla@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;
as well as URLs for NNTP newsgroup(s).