From: Sasha Levin <sashal@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: "Matthias Brugger" <matthias.bgg@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Fabien Parent" <fparent@baylibre.com>,
"Miles Chen" <miles.chen@mediatek.com>,
"Macpaul Lin" <macpaul.lin@mediatek.com>,
"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
"Sam Shih" <sam.shih@mediatek.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Jieyy Yang" <jieyy.yang@mediatek.com>,
"Tinghan Shen" <tinghan.shen@mediatek.com>,
"Seiya Wang" <seiya.wang@mediatek.com>,
soc@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
stable@vger.kernel.org,
"Eugen Hristev" <eugen.hristev@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Subject: Re: [PATCH 0/5] MediaTek: Update MAINTAINERS and dts fixes for v6.7
Date: Tue, 3 Oct 2023 08:45:07 -0400 [thread overview]
Message-ID: <ZRwM06dwpF/7wEs5@sashalap> (raw)
In-Reply-To: <20231003-mediatek-fixes-v6-7-v1-0-dad7cd62a8ff@collabora.com>
On Tue, Oct 03, 2023 at 01:13:42PM +0200, AngeloGioacchino Del Regno wrote:
>Hello SoC maintainers,
>
>As suggested by Arnd in [1], I am sending an update to the MAINTAINERS
>file, adding myself to the MediaTek SoC maintainers, and some urgent
>bugfixes for MediaTek devicetrees.
Just curious: if it's urgent, and there are patches cc'ed to stable, why
wait for 6.7 rather than one of the 6.6 -rc cycles?
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-10-03 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 11:13 [PATCH 0/5] MediaTek: Update MAINTAINERS and dts fixes for v6.7 AngeloGioacchino Del Regno
2023-10-03 11:13 ` [PATCH 1/5] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer AngeloGioacchino Del Regno
2023-10-03 15:20 ` Mathieu Poirier
2023-10-03 11:13 ` [PATCH 2/5] arm64: dts: mediatek: mt8195-demo: fix the memory size to 8GB AngeloGioacchino Del Regno
2023-10-03 11:13 ` [PATCH 3/5] arm64: dts: mediatek: mt8195-demo: update and reorder reserved memory regions AngeloGioacchino Del Regno
2023-10-03 11:13 ` [PATCH 4/5] arm64: dts: mediatek: fix t-phy unit name AngeloGioacchino Del Regno
2023-10-03 11:13 ` [PATCH 5/5] arm64: dts: mediatek: mt8195: Set DSU PMU status to fail AngeloGioacchino Del Regno
2023-10-03 11:37 ` [PATCH 0/5] MediaTek: Update MAINTAINERS and dts fixes for v6.7 AngeloGioacchino Del Regno
2023-10-03 12:45 ` Sasha Levin [this message]
2023-10-03 14:19 ` 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=ZRwM06dwpF/7wEs5@sashalap \
--to=sashal@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunfeng.yun@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eugen.hristev@collabora.com \
--cc=fparent@baylibre.com \
--cc=frank-w@public-files.de \
--cc=jieyy.yang@mediatek.com \
--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=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=miles.chen@mediatek.com \
--cc=nfraprado@collabora.com \
--cc=robh+dt@kernel.org \
--cc=sam.shih@mediatek.com \
--cc=seiya.wang@mediatek.com \
--cc=soc@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tinghan.shen@mediatek.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;
as well as URLs for NNTP newsgroup(s).