From: Will Deacon <will@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
Jiucheng Xu <jiucheng.xu@amlogic.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Kevin Hilman <khilman@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-amlogic@lists.infradead.org,
Chris Healy <healych@amazon.com>,
linux-kernel@vger.kernel.org, Chris Healy <cphealy@gmail.com>,
Kelvin Zhang <kelvin.zhang@amlogic.com>,
Jianxin Pan <jianxin.pan@amlogic.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] perf/amlogic: Fix build error for x86_64 allmodconfig
Date: Tue, 22 Nov 2022 11:19:57 +0000 [thread overview]
Message-ID: <166911295884.1006209.12453209108880298807.b4-ty@kernel.org> (raw)
In-Reply-To: <20221122084028.572494-1-jiucheng.xu@amlogic.com>
On Tue, 22 Nov 2022 16:40:28 +0800, Jiucheng Xu wrote:
> The driver misses including <linux/io.h>. It causes
> compiling error "implicit declaration of function
> 'readl' and 'writel'" when make X86_64 allmodconfig.
>
> Amlogic meson G12 SoC DDR PMU driver")'
>
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] perf/amlogic: Fix build error for x86_64 allmodconfig
https://git.kernel.org/will/c/9d1d5cb32314
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2022-11-22 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 8:40 Jiucheng Xu
2022-11-22 11:19 ` Will Deacon [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=166911295884.1006209.12453209108880298807.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cphealy@gmail.com \
--cc=healych@amazon.com \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=jiucheng.xu@amlogic.com \
--cc=kelvin.zhang@amlogic.com \
--cc=kernel-team@android.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.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®