From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Frank Wunderlich <frank-w@public-files.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, erkin.bozoglu@xeront.com
Subject: Re: [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5
Date: Sat, 18 Feb 2023 10:00:19 +0300 [thread overview]
Message-ID: <c3ab9a9b-3eb2-8fb0-d5d7-c0b7c684d3a7@arinc9.com> (raw)
In-Reply-To: <20230210182505.24597-1-arinc.unal@arinc9.com>
Frank, I think Matthias is waiting for your approval on this patch
series. Is this series fine by you?
Arınç
next prev parent reply other threads:[~2023-02-18 7:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:25 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 1/5] arm: dts: mt7623: add gmacs to mt7623.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 2/5] arm: dts: mt7623: add mt7530 switch to mt7623a.dtsi arinc9.unal
2023-02-10 18:25 ` [PATCH v3 3/5] arm: dts: mt7623: change mt7530 switch address arinc9.unal
2023-02-10 18:25 ` [PATCH v3 4/5] arm: dts: mt7623: enable flow control on port@6 arinc9.unal
2023-02-10 18:25 ` [PATCH v3 5/5] arm: dts: mt7623: add port@5 as CPU port arinc9.unal
2023-02-18 7:00 ` Arınç ÜNAL [this message]
2023-02-18 10:24 ` Aw: Re: [PATCH v3 0/5] arm: dts: mt7623: relocate gmacs, mt7530 switch, and add port@5 Frank Wunderlich
2023-02-18 10:49 ` Arınç ÜNAL
2023-02-18 12:18 ` Aw: " Frank Wunderlich
2023-02-18 17:02 ` Arınç ÜNAL
2023-02-18 19:11 ` Frank Wunderlich
2023-02-18 19:34 ` Arınç ÜNAL
2023-02-19 13:52 ` Aw: " Frank Wunderlich
2023-04-12 12:49 ` Frank Wunderlich
2023-04-12 14:31 ` Arınç ÜNAL
2023-04-12 15:11 ` Aw: " Frank Wunderlich
2023-04-12 16:21 ` Arınç ÜNAL
2023-04-12 16:53 ` Aw: " Frank Wunderlich
2023-04-12 17:06 ` Arınç ÜNAL
2023-05-29 13:40 ` Matthias Brugger
2023-06-03 10:48 ` Arınç ÜNAL
2023-06-09 14:34 ` Matthias Brugger
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=c3ab9a9b-3eb2-8fb0-d5d7-c0b7c684d3a7@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=erkin.bozoglu@xeront.com \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®