From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev,
Garmin . Chang <Garmin.Chang@mediatek.com>,
Chen-Yu Tsai <wenst@chromium.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v3] clk: mediatek: Use right match table, include mod_devicetable
Date: Tue, 04 Apr 2023 13:48:04 -0700 [thread overview]
Message-ID: <d415decc59aac39be25cd7916ae650cb.sboyd@kernel.org> (raw)
In-Reply-To: <20230404204553.1256263-1-sboyd@kernel.org>
Quoting Stephen Boyd (2023-04-04 13:45:53)
> This is copy/pasta that breaks modular builds. Fix the match table to
> use the right pointer, or the right device table type. And while we're
> including the header, fix the order to be linux, dt-bindings, and
> finally local.
>
> Cc: Garmin.Chang <Garmin.Chang@mediatek.com>
> Cc: Chen-Yu Tsai <wenst@chromium.org>
> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> Fixes: f42b9e9a43e3 ("clk: mediatek: Add MT8188 wpesys clock support")
> Fixes: 0d2f2cefba64 ("clk: mediatek: Add MT8188 adsp clock support")
> Fixes: e4aaa60eae16 ("clk: mediatek: Add MT8188 vdosys0 clock support")
> Fixes: cfa4609f9bbe ("clk: mediatek: Add MT8188 vdosys1 clock support")
> Fixes: bb87c1109ce2 ("clk: mediatek: Add MT8188 vencsys clock support")
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/oe-kbuild-all/202304011039.UBDX1UOT-lkp@intel.com/
> Link: https://lore.kernel.org/oe-kbuild-all/202304020649.QO2HlpD5-lkp@intel.com/
> Link: https://lore.kernel.org/oe-kbuild-all/202304021055.WDhQPcoS-lkp@intel.com/
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
Applied to clk-next
prev parent reply other threads:[~2023-04-04 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 20:45 [PATCH v3] clk: mediatek: Use right match table, include mod_devicetable Stephen Boyd
2023-04-04 20:48 ` Stephen Boyd [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=d415decc59aac39be25cd7916ae650cb.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=Garmin.Chang@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
--cc=wenst@chromium.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