devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
Cc: krzysztof.kozlowski+dt@linaro.org, matthias.bgg@gmail.com,
	mturquette@baylibre.com, sboyd@kernel.org,
	p.zabel@pengutronix.de, y.oudjana@protonmail.com,
	jason-jh.lin@mediatek.com, ck.hu@mediatek.com,
	fparent@baylibre.com, rex-bc.chen@mediatek.com,
	tinghan.shen@mediatek.com, chun-jie.chen@mediatek.com,
	weiyi.lu@mediatek.com, ikjn@chromium.org,
	miles.chen@mediatek.com, sam.shih@mediatek.com,
	wenst@chromium.org, bgolaszewski@baylibre.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-clk@vger.kernel.org,
	konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
	martin.botka@somainline.org,
	~postmarketos/upstreaming@lists.sr.ht,
	phone-devel@vger.kernel.org, paul.bouchara@somainline.org,
	kernel@collabora.com
Subject: Re: [PATCH 0/5] MediaTek Helio X10 MT6795 - Clock drivers
Date: Tue, 17 May 2022 19:47:06 -0500	[thread overview]
Message-ID: <20220518004706.GA1950724-robh@kernel.org> (raw)
In-Reply-To: <7ed1b785-389f-9730-4686-bc6b85cc8f6d@collabora.com>

On Fri, May 13, 2022 at 06:54:49PM +0200, AngeloGioacchino Del Regno wrote:
> Il 13/05/22 18:50, AngeloGioacchino Del Regno ha scritto:
> > In an effort to give some love to the apparently forgotten MT6795 SoC,
> > I am upstreaming more components that are necessary to support platforms
> > powered by this one apart from a simple boot to serial console.
> > 
> > This (very big) series introduces system clock, multimedia clock drivers
> > (including resets) for this SoC.
> > 
> > Tested on a MT6795 Sony Xperia M5 (codename "Holly") smartphone.
> > 
> 
> I forgot to add context to the cover letter for this series, so I'm adding that
> in reply to myself.
> 
> This series depends on Chen-Yu's clocks cleanup series (clk_hw) [1] *and* on
> Rex-BC's MTK reset binding-cleanup series [2].
> 
> [1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=640122
> [2] https://patchwork.kernel.org/project/linux-mediatek/list/?series=637849

As well as the schema conversions in my tree. So I need to apply some of 
this? Provide maintainers with details on how exactly a series should 
be applied if there's a mixture of subsystems, dependencies already 
applied, and dependencies not yet applied. I'm just going to wait for 
explicit requests of what I need to apply as there's already too much 
Mediatek stuff floating around. Last merge window was a mess too.

Rob

      reply	other threads:[~2022-05-18  0:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 16:50 [PATCH 0/5] MediaTek Helio X10 MT6795 - Clock drivers AngeloGioacchino Del Regno
2022-05-13 16:50 ` [PATCH 1/5] dt-bindings: mediatek: Document MT6795 system controllers bindings AngeloGioacchino Del Regno
2022-05-16 16:03   ` Rob Herring
2022-05-13 16:50 ` [PATCH 2/5] dt-bindings: clock: Add MediaTek Helio X10 MT6795 clock bindings AngeloGioacchino Del Regno
2022-05-13 16:50 ` [PATCH 3/5] dt-bindings: reset: Add bindings for MT6795 Helio X10 reset controllers AngeloGioacchino Del Regno
2022-05-13 16:50 ` [PATCH 4/5] dt-bindings: arm: mediatek: Add clock driver bindings for MT6795 AngeloGioacchino Del Regno
2022-05-13 20:48   ` Rob Herring
2022-05-16 17:28   ` Rob Herring
2022-05-17  7:48     ` AngeloGioacchino Del Regno
2022-05-13 16:50 ` [PATCH 5/5] clk: mediatek: Add MediaTek Helio X10 MT6795 clock drivers AngeloGioacchino Del Regno
2022-05-13 22:00   ` kernel test robot
2022-05-13 23:01   ` kernel test robot
2022-05-16 11:30   ` Matthias Brugger
2022-05-17  8:07     ` AngeloGioacchino Del Regno
2022-05-17  8:48       ` Matthias Brugger
2022-05-17  8:59         ` AngeloGioacchino Del Regno
2022-05-13 16:54 ` [PATCH 0/5] MediaTek Helio X10 MT6795 - Clock drivers AngeloGioacchino Del Regno
2022-05-18  0:47   ` Rob Herring [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=20220518004706.GA1950724-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=chun-jie.chen@mediatek.com \
    --cc=ck.hu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fparent@baylibre.com \
    --cc=ikjn@chromium.org \
    --cc=jason-jh.lin@mediatek.com \
    --cc=kernel@collabora.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=matthias.bgg@gmail.com \
    --cc=miles.chen@mediatek.com \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=paul.bouchara@somainline.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=rex-bc.chen@mediatek.com \
    --cc=sam.shih@mediatek.com \
    --cc=sboyd@kernel.org \
    --cc=tinghan.shen@mediatek.com \
    --cc=weiyi.lu@mediatek.com \
    --cc=wenst@chromium.org \
    --cc=y.oudjana@protonmail.com \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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).