From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-clk@vger.kernel.org
Cc: john@phrozen.org, linux-staging@lists.linux.dev,
gregkh@linuxfoundation.org, neil@brown.name,
p.zabel@pengutronix.de, linux-kernel@vger.kernel.org,
sboyd@kernel.org, erkin.bozoglu@xeront.com,
Luiz Angelo Daros de Luca <luizluca@gmail.com>
Subject: Re: [PATCH v8 0/4] clk: ralink: make system controller a reset provider
Date: Wed, 19 Jan 2022 16:27:21 +0300 [thread overview]
Message-ID: <d46fcc03-40f1-edbf-e966-e35aabf84111@arinc9.com> (raw)
In-Reply-To: <20220110114930.1406665-1-sergio.paracuellos@gmail.com>
This series fixes the SPI & MDIO probing issues we were having with our
mt7621 board.
Tested-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Cheers.
Arınç
next prev parent reply other threads:[~2022-01-19 13:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 11:49 Sergio Paracuellos
2022-01-10 11:49 ` [PATCH v8 1/4] dt-bindings: reset: add dt binding header for Mediatek MT7621 resets Sergio Paracuellos
2022-01-10 11:49 ` [PATCH v8 2/4] dt-bindings: clock: mediatek,mt7621-sysc: add '#reset-cells' property Sergio Paracuellos
2022-01-25 1:10 ` Stephen Boyd
2022-01-10 11:49 ` [PATCH v8 3/4] clk: ralink: make system controller node a reset provider Sergio Paracuellos
2022-01-10 11:54 ` Philipp Zabel
2022-01-25 1:11 ` Stephen Boyd
2022-01-25 1:14 ` Stephen Boyd
2022-01-25 6:27 ` Sergio Paracuellos
2022-01-10 11:49 ` [PATCH v8 4/4] staging: mt7621-dts: align resets with binding documentation Sergio Paracuellos
2022-01-10 11:54 ` Philipp Zabel
2022-01-26 11:46 ` Sergio Paracuellos
2022-01-26 12:16 ` Greg KH
2022-01-19 13:27 ` Arınç ÜNAL [this message]
2022-01-19 13:55 ` [PATCH v8 0/4] clk: ralink: make system controller a reset provider Sergio Paracuellos
2022-01-26 12:06 ` Greg KH
2022-01-26 12:08 ` Sergio Paracuellos
2022-01-26 12:14 ` Greg KH
2022-01-26 12:45 ` Sergio Paracuellos
2022-02-05 2:55 ` Stephen Boyd
2022-02-05 7:31 ` Sergio Paracuellos
2022-02-10 6:44 ` Sergio Paracuellos
2022-02-10 6:55 ` Greg KH
2022-02-10 9:52 ` Sergio Paracuellos
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=d46fcc03-40f1-edbf-e966-e35aabf84111@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=erkin.bozoglu@xeront.com \
--cc=gregkh@linuxfoundation.org \
--cc=john@phrozen.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luizluca@gmail.com \
--cc=neil@brown.name \
--cc=p.zabel@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=sergio.paracuellos@gmail.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
Powered by JetHome