mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: mediatek: Remove unused configs MACH_MT6592 and MACH_MT6592
Date: Mon, 20 Mar 2023 15:42:49 +0100	[thread overview]
Message-ID: <01964ce6-7a91-a86e-6ae0-73ab177ba01a@collabora.com> (raw)
In-Reply-To: <20230320132634.17331-1-lukas.bulwahn@gmail.com>

Il 20/03/23 14:26, Lukas Bulwahn ha scritto:
> Commit ad8a221e1f49 ("ARM: mediatek: Add config options for mediatek SoCs.")
> adds four configs MACH_MT6592, MACH_MT6592, MACH_MT8127 and MACH_MT8127 for
> foreseen future use in the MediaTek pinctrl driver. As of now, nine years

........

> after that commit, the configs MACH_MT8127 and MACH_MT8127 are used for
> that purpose, but tconfigs MACH_MT6592 and MACH_MT6592 have not been used.
> 
> Remove the unused configs MACH_MT6592 and MACH_MT6592.

I say that there's some confusion in the commit description... :-)

Please fix.

Thanks,
Angelo

> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>   arch/arm/mach-mediatek/Kconfig | 8 --------
>   1 file changed, 8 deletions(-)
> 
> diff --git a/arch/arm/mach-mediatek/Kconfig b/arch/arm/mach-mediatek/Kconfig
> index 35a3430c7942..521af13a79d8 100644
> --- a/arch/arm/mach-mediatek/Kconfig
> +++ b/arch/arm/mach-mediatek/Kconfig
> @@ -15,14 +15,6 @@ config MACH_MT2701
>   	bool "MediaTek MT2701 SoCs support"
>   	default ARCH_MEDIATEK
>   
> -config MACH_MT6589
> -	bool "MediaTek MT6589 SoCs support"
> -	default ARCH_MEDIATEK
> -
> -config MACH_MT6592
> -	bool "MediaTek MT6592 SoCs support"
> -	default ARCH_MEDIATEK
> -
>   config MACH_MT7623
>   	bool "MediaTek MT7623 SoCs support"
>   	default ARCH_MEDIATEK



      reply	other threads:[~2023-03-20 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-20 13:26 Lukas Bulwahn
2023-03-20 14:42 ` AngeloGioacchino Del Regno [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=01964ce6-7a91-a86e-6ae0-73ab177ba01a@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=lukas.bulwahn@gmail.com \
    --cc=matthias.bgg@gmail.com \
    /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®