From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: arinc9.unal@gmail.com
Cc: "John Crispin" <john@phrozen.org>,
"Arınç ÜNAL" <arinc.unal@arinc9.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
"Sergio Paracuellos" <sergio.paracuellos@gmail.com>,
erkin.bozoglu@xeront.com
Subject: Re: [PATCH] mips: ralink: make SOC_MT7621 select PINCTRL_MT7621 and fix help section
Date: Sun, 5 Feb 2023 17:02:22 +0100 [thread overview]
Message-ID: <20230205160222.GA4459@alpha.franken.de> (raw)
In-Reply-To: <20230204214249.134937-1-arinc.unal@arinc9.com>
On Sun, Feb 05, 2023 at 12:42:49AM +0300, arinc9.unal@gmail.com wrote:
> From: Arınç ÜNAL <arinc.unal@arinc9.com>
>
> The dt-binding of the MT7621 SoC uses the pinctrl driver. Therefore, have
> this driver selected by default.
>
> The help section for SOC_MT7621 exceeds 80 columns which is the preferred
> limit of a single line. A tab character is 8 columns. Rearrange the text
> accordingly.
>
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
> ---
> arch/mips/ralink/Kconfig | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/mips/ralink/Kconfig b/arch/mips/ralink/Kconfig
> index f9fe15630abb..06031796c87b 100644
> --- a/arch/mips/ralink/Kconfig
> +++ b/arch/mips/ralink/Kconfig
> @@ -54,10 +54,11 @@ choice
> select HAVE_PCI
> select PCI_DRIVERS_GENERIC
> select SOC_BUS
> + select PINCTRL_MT7621
>
> help
> - The MT7621 system-on-a-chip includes an 880 MHz MIPS1004Kc dual-core CPU,
> - a 5-port 10/100/1000 switch/PHY and one RGMII.
> + The MT7621 system-on-a-chip includes an 880 MHz MIPS1004Kc
> + dual-core CPU, a 5-port 10/100/1000 switch/PHY and one RGMII.
> endchoice
>
> choice
> --
> 2.37.2
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2023-02-05 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 21:42 arinc9.unal
2023-02-05 16:02 ` Thomas Bogendoerfer [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=20230205160222.GA4459@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=arinc.unal@arinc9.com \
--cc=arinc9.unal@gmail.com \
--cc=erkin.bozoglu@xeront.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=sergio.paracuellos@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®