From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rob Herring <robh@kernel.org>
Cc: Frank Wunderlich <linux@fw-web.de>,
Linus Walleij <linus.walleij@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@kernel.org>,
Frank Wunderlich <frank-w@public-files.de>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v7 3/5] dt-bindings: pinctrl: add binding for MT7988 SoC
Date: Thu, 19 Dec 2024 13:41:56 +0100 [thread overview]
Message-ID: <e9fb2634-5b47-4f68-ad7c-26a4f52d0df8@collabora.com> (raw)
In-Reply-To: <20241219123441.GA4016373-robh@kernel.org>
Il 19/12/24 13:34, Rob Herring ha scritto:
> On Thu, Dec 19, 2024 at 12:56:23PM +0100, AngeloGioacchino Del Regno wrote:
>> Il 17/12/24 09:54, Frank Wunderlich ha scritto:
>>> From: Frank Wunderlich <frank-w@public-files.de>
>>>
>>> This adds bindings for MT7988 pinctrl driver.
>>>
>>> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
>>> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>
>> DT binding maintainers, can you please review this patch and eventually release
>> an Ack so that I can take it through the MediaTek tree along with the devicetree
>> changes?
>
> It's been 2 days... If you want to know the status and where you are in
> the queue, you can check patchwork[1]. But guess what, you're #1.
>
> Rob
>
> [1] https://patchwork.ozlabs.org/project/devicetree-bindings/list/
Rob, I was checking the patches to apply to the MTK trees and while in the
process I didn't notice that this one was sent that early.
Sending a ping after a short time wasn't intentional. Sorry for that.
Cheers,
Angelo
next prev parent reply other threads:[~2024-12-19 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 8:54 [PATCH v7 0/5] Add pinctrl support for mt7988 Frank Wunderlich
2024-12-17 8:54 ` [PATCH v7 1/5] pinctrl: mediatek: add support for MTK_PULL_PD_TYPE Frank Wunderlich
2024-12-17 8:54 ` [PATCH v7 2/5] pinctrl: mediatek: add MT7988 pinctrl driver Frank Wunderlich
2024-12-17 8:54 ` [PATCH v7 3/5] dt-bindings: pinctrl: add binding for MT7988 SoC Frank Wunderlich
2024-12-19 11:56 ` AngeloGioacchino Del Regno
2024-12-19 12:34 ` Rob Herring
2024-12-19 12:41 ` AngeloGioacchino Del Regno [this message]
2024-12-19 12:53 ` Rob Herring (Arm)
2024-12-17 8:54 ` [PATCH v7 4/5] arm64: dts: mediatek: mt7988: Add pinctrl support Frank Wunderlich
2024-12-17 8:54 ` [PATCH v7 5/5] arm64: dts: mediatek: mt7988a-bpi-r4: Add pinctrl subnodes for bpi-r4 Frank Wunderlich
2024-12-18 14:12 ` [PATCH v7 0/5] Add pinctrl support for mt7988 AngeloGioacchino Del Regno
2024-12-27 8:23 ` Linus Walleij
2025-01-02 12:46 ` (subset) " AngeloGioacchino Del Regno
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=e9fb2634-5b47-4f68-ad7c-26a4f52d0df8@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=sean.wang@kernel.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