From: Marc Zyngier <maz@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: u-boot@lists.denx.de, Vladimir Oltean <vladimir.oltean@nxp.com>,
Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
Bharat Gooty <bharat.gooty@broadcom.com>,
Rayagonda Kokatanur <rayagonda.kokatanur@broadcom.com>,
Simon Glass <sjg@chromium.org>,
Priyanka Jain <priyanka.jain@nxp.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH 1/2] Revert "arm64: Layerscape: Survive LPI one-way reset workaround"
Date: Thu, 28 Oct 2021 22:11:37 +0100 [thread overview]
Message-ID: <87ilxgua5y.wl-maz@kernel.org> (raw)
In-Reply-To: <20211027165454.1501398-2-michael@walle.cc>
On Wed, 27 Oct 2021 17:54:53 +0100,
Michael Walle <michael@walle.cc> wrote:
>
> From: Tom Rini <trini@konsulko.com>
>
> Ad-hoc bindings that are not part of the upstream device tree / bindings
> are not allowed in-tree. Only bindings that are in-progress with
> upstream and then re-synced once agreed upon are.
>
> This reverts commit af288cb291da3abef6be0875527729296f7de7a0.
>
> Cc: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
> Cc: Priyanka Jain <priyanka.jain@nxp.com>
> Reported-by: Michael Walle <michael@walle.cc>
> Signed-off-by: Tom Rini <trini@konsulko.com>
> ---
> arch/arm/cpu/armv8/fsl-layerscape/soc.c | 18 +-----------------
> arch/arm/dts/fsl-ls1028a.dtsi | 6 ------
> arch/arm/dts/fsl-ls1088a.dtsi | 6 ------
> arch/arm/dts/fsl-ls2080a.dtsi | 6 ------
> arch/arm/dts/fsl-lx2160a.dtsi | 6 ------
> 5 files changed, 1 insertion(+), 41 deletions(-)
Acked-by: Marc Zyngier <maz@kernel.org>
I have a number of comments on the second patch, but getting rid of
this gunk is a good start.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-10-28 21:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 16:54 [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree Michael Walle
2021-10-27 16:54 ` [PATCH 1/2] Revert "arm64: Layerscape: Survive LPI one-way reset workaround" Michael Walle
2021-10-28 21:11 ` Marc Zyngier [this message]
2021-10-31 16:23 ` Tom Rini
2021-10-27 16:54 ` [PATCH 2/2] Revert "arch: arm: use dt and UCLASS_SYSCON to get gic lpi details" Michael Walle
2021-10-28 21:09 ` Marc Zyngier
2021-10-28 21:35 ` Tom Rini
2021-10-29 11:49 ` Michael Walle
2021-10-29 12:00 ` Marc Zyngier
2021-10-31 16:45 ` Z.Q. Hou
2021-10-31 16:58 ` Michael Walle
2021-11-01 9:38 ` Marc Zyngier
2021-10-31 16:24 ` Tom Rini
2021-10-28 9:01 ` [PATCH 0/2] arch: arm: gic-v3-its: stop abusing the device tree Marc Zyngier
2021-10-28 9:20 ` Bharat Gooty
2021-10-28 9:49 ` Marc Zyngier
2021-10-28 10:27 ` Bharat Gooty
2021-10-28 14:39 ` Marc Zyngier
2021-10-28 11:21 ` Michael Walle
2021-10-28 11:35 ` Bharat Gooty
2021-10-28 12:09 ` Michael Walle
2021-10-28 14:42 ` Marc Zyngier
2021-10-28 12:31 ` Tom Rini
2021-10-28 13:38 ` Marc Zyngier
2021-10-28 13:51 ` Tom Rini
2021-10-28 22:36 ` Simon Glass
2021-10-29 11:54 ` Michael Walle
2021-10-29 21:17 ` Simon Glass
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=87ilxgua5y.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bharat.gooty@broadcom.com \
--cc=michael@walle.cc \
--cc=priyanka.jain@nxp.com \
--cc=rayagonda.kokatanur@broadcom.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.