From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: linux-mips@vger.kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, matthias.bgg@gmail.com,
angelogioacchino.delregno@collabora.com,
harveyhuntnexus@gmail.com, devicetree@vger.kernel.org,
yangshiji66@outlook.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] mips: dts: ralink: mt7628a: update system controller node and its consumers
Date: Thu, 27 Feb 2025 11:03:32 +0100 [thread overview]
Message-ID: <Z8A4dGWgGn39S0Ek@alpha.franken.de> (raw)
In-Reply-To: <20250224053411.924015-1-sergio.paracuellos@gmail.com>
On Mon, Feb 24, 2025 at 06:34:11AM +0100, Sergio Paracuellos wrote:
> Current MT7628A device tree file system controller node is wrong since it is
> not matching bindings. Hence, update it to match current bindings updating
> it also to use new introduced clock constants.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> Hi Thomas,
>
> This is the missing patch to be applied in the series [0] because of some
> build errors.
>
> Changes in v4:
> - update syntax in mail file from /include/ to #include.
> - Fix build errors in 'usb-phy' node.
>
> Thanks a lot.
>
> Best regards,
> Sergio Paracuellos
>
> [0]: https://lore.kernel.org/linux-mips/CAMhs-H-8N766PMZMwmV8B3e=65pPZHA4ntnRWDMoqR-U_xULfA@mail.gmail.com/T/#mab23157e03609456bb59d3b5dfc71fe16359a419
>
> .../ralink/gardena_smart_gateway_mt7688.dts | 2 +-
> arch/mips/boot/dts/ralink/mt7628a.dtsi | 40 ++++++++++++-------
> arch/mips/boot/dts/ralink/omega2p.dts | 2 +-
> 3 files changed, 27 insertions(+), 17 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2025-02-27 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 5:34 [PATCH v4] mips: dts: ralink: mt7628a: update system controller node and its consumers Sergio Paracuellos
2025-02-27 10:03 ` Thomas Bogendoerfer [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=Z8A4dGWgGn39S0Ek@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=harveyhuntnexus@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sergio.paracuellos@gmail.com \
--cc=yangshiji66@outlook.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