From: Petr Vorel <petr.vorel@gmail.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: "Enric Balletbo i Serra" <enric.balletbo@collabora.com>,
linux-kernel@vger.kernel.org,
"Collabora Kernel ML" <kernel@collabora.com>,
linux-mediatek@lists.infradead.org, drinkcat@chromium.org,
hsinyi@chromium.org, "Arnd Bergmann" <arnd@arndb.de>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Guido Günther" <agx@sigxcpu.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"Max Krummenacher" <max.oss.09@gmail.com>,
"Michael Walle" <michael@walle.cc>, "Nishanth Menon" <nm@ti.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Will Deacon" <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Luo Longjun" <luolongjun@huawei.com>
Subject: Re: [PATCH] arm64: defconfig: Do not override the MTK_PMIC_WRAP symbol
Date: Fri, 11 Jun 2021 23:48:56 +0200 [thread overview]
Message-ID: <YMPaSD45DOFMsNFW@pevik> (raw)
In-Reply-To: <cb9c85d5-3467-c235-93cd-be23fb6e0a03@gmail.com>
Hi all,
> On 23/04/2021 09:52, Enric Balletbo i Serra wrote:
> > Commit 'fbbe38309d56 ("arm64: defconfig: Allow mt8173-based boards to boot
> > from usb")' added the MTK_PMIC_WRAP config built-in. It needs to be
> > built-in in order to be able to boot from USB or the MMC without needing
> > a ramdisk, but that symbol was already defined as a module so now we are
> > getting the following warning:
> > arch/arm64/configs/defconfig:996:warning: override: reassigning to symbol MTK_PMIC_WRAP
> > Remove the MTK_PMIC_WRAP=m from the defconfig to remove the error.
> > Fixes: fbbe38309d56 ("arm64: defconfig: Allow mt8173-based boards to boot from usb")
> > Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Applied to v5.13-next/defconfig
I'm sorry, please ignore my useless Reviewed-by: tag.
I was searching in arm64 git [1] and overlooked the date.
I see it was merged into Matthias' git tree [2] month ago.
Kind regards,
Petr
[1] https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/commit/?h=v5.13-next-defconfig&id=f0e70d4946332c681ceaba940652f30c7c33473d
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-11 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 7:52 [PATCH] arm64: defconfig: Do not override the MTK_PMIC_WRAP symbol Enric Balletbo i Serra
2021-05-14 7:54 ` Matthias Brugger
2021-06-11 21:48 ` Petr Vorel [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=YMPaSD45DOFMsNFW@pevik \
--to=petr.vorel@gmail.com \
--cc=agx@sigxcpu.org \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=drinkcat@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=hsinyi@chromium.org \
--cc=kernel@collabora.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luolongjun@huawei.com \
--cc=matthias.bgg@gmail.com \
--cc=max.oss.09@gmail.com \
--cc=michael@walle.cc \
--cc=nm@ti.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=shawnguo@kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).