linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Luo Longjun <luolongjun@huawei.com>,
	will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, sangyan@huawei.com,
	ningyu9@huawei.com, luchunhua@huawei.com
Subject: Re: [PATCH] arm64: configs: remove redundant CONFIG_MTK_PMIC_WRAP
Date: Fri, 11 Jun 2021 23:39:23 +0200	[thread overview]
Message-ID: <YMPYC5OAEh5vJQwv@pevik> (raw)
In-Reply-To: <aa3d0bf1-8330-42e0-d11b-c554194c3b81@gmail.com>

Hi,

> Hi all,

> On 11/05/2021 22:04, Enric Balletbo i Serra wrote:
> > Hi Catalin,

> > Thanks for cc'ing me.

> > On 11/5/21 19:20, Catalin Marinas wrote:
> >> On Sat, May 08, 2021 at 02:24:10AM +0800, Luo Longjun wrote:
> >>> When I compile kernel in ARM64, it produces the following output:

> >>> *** Default configuration is based on 'defconfig'
> >>> arch/arm64/configs/defconfig:1018:warning: override: reassigning to
> >>> symbol MTK_PMIC_WRAP

> >>> After checking defcofnig, I found two CONFIG_MTK_PMIC_WRAP options.

> >>> Signed-off-by: Luo Longjun <luolongjun@huawei.com>
> >>> ---
> >>>  arch/arm64/configs/defconfig | 1 -
> >>>  1 file changed, 1 deletion(-)

> >>> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> >>> index 08c6f769df9a..9907a431db0d 100644
> >>> --- a/arch/arm64/configs/defconfig
> >>> +++ b/arch/arm64/configs/defconfig
> >>> @@ -491,7 +491,6 @@ CONFIG_SPI_S3C64XX=y
> >>>  CONFIG_SPI_SH_MSIOF=m
> >>>  CONFIG_SPI_SUN6I=y
> >>>  CONFIG_SPI_SPIDEV=m
> >>> -CONFIG_MTK_PMIC_WRAP=m
> >>>  CONFIG_SPMI=y
> >>>  CONFIG_PINCTRL_SINGLE=y
> >>>  CONFIG_PINCTRL_MAX77620=y

> >> Adding Matthias and Enric. This change looks fine to me but I think it
> >> should go in via the arm-soc tree. Commit 9fd5449e061e introduced the =m
> >> option while commit fbbe38309d56 introduced the =y variant.

> >> You could add:

> >> Fixes: fbbe38309d56 ("arm64: defconfig: Allow mt8173-based boards to boot from usb")

Reviewed-by: Petr Vorel <petr.vorel@gmail.com>

I was going to send fix myself, I'd prefer also y, but weren't 100% sure sure.

For a record:

* CONFIG_MTK_PMIC_WRAP=m committed by author in 2021-01-04, merged 2021-01-31 15:31:01
9fd5449e061e ("arm64: configs: Support pwrap on Mediatek MT6779 platform")
sent: 4 Jan 2021
https://lore.kernel.org/r/1609747703-27207-3-git-send-email-argus.lin@mediatek.com
Applied to v5.11-next/defconfig 31 Jan 2021 15:32:26 by Matthias Brugger <matthias.bgg@gmail.com>
https://lore.kernel.org/linux-devicetree/5d5a67a5-ac2d-9ef9-b20c-66cbd55ebb8f@gmail.com/

* CONFIG_MTK_PMIC_WRAP=y was committed by author in 2021-03-31 11:06:57, merged 2021-03-31 12:12:59
fbbe38309d56 ("arm64: defconfig: Allow mt8173-based boards to boot from usb")
sent: 31 Mar 2021 11:06:57
https://lore.kernel.org/r/20210331090659.4169966-1-enric.balletbo@collabora.com
But originally sent: 9 Feb 2021 10:11:11
https://lore.kernel.org/lkml/20210209091112.2075478-1-enric.balletbo@collabora.com/

Kind regards,
Petr

> > I sent the same patch some time ago [1].

> > I agree, either land this patch or mine. In any case,

> > Reviewed-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>

> > Matthias is this something that should go through your tree?


> Yes, this should go through my tree. I'll take care of it.

> Regards,
> Matthias

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-06-11 21:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 18:24 [PATCH] arm64: configs: remove redundant CONFIG_MTK_PMIC_WRAP Luo Longjun
2021-05-11 17:20 ` Catalin Marinas
2021-05-11 20:04   ` Enric Balletbo i Serra
2021-05-14  7:42     ` Matthias Brugger
2021-06-11 21:39       ` Petr Vorel [this message]
2021-06-14  8:58         ` Matthias Brugger

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=YMPYC5OAEh5vJQwv@pevik \
    --to=petr.vorel@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=enric.balletbo@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luchunhua@huawei.com \
    --cc=luolongjun@huawei.com \
    --cc=matthias.bgg@gmail.com \
    --cc=ningyu9@huawei.com \
    --cc=sangyan@huawei.com \
    --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).