linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
	"Zhicheng Fan" <b32736@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"Kumar Gala" <galak@kernel.crashing.org>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"Scott Wood" <oss@buserror.net>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Pali Rohár" <pali@kernel.org>,
	"Timur Tabi" <timur@freescale.com>
Subject: Re: [PATCH] powerpc/85xx: Fix typo in code comment
Date: Fri, 24 Nov 2023 13:08:25 +0000	[thread overview]
Message-ID: <4ce802db-b6d0-4eec-9ae2-5383a6f01843@csgroup.eu> (raw)
In-Reply-To: <20231124100241.660374-1-dario.binacchi@amarulasolutions.com>



Le 24/11/2023 à 11:02, Dario Binacchi a écrit :
> s/singals/signals/

Is that really worth it to spend time on such a change ?

By sending such a patch, you require people to spend time reviewing your 
patch, then maintainer has to spend time handling your patch.
Furthermore, as you added a Fixes: tag, LTS maintainers will have to 
spend time handling that too.

Do you really think that this typo is worth a patch ?

This kind of tiny error should be fixed through a more significant patch 
adressing this file. But it is not worth a patch on its own.

Christophe


> 
> Fixes: 04e358d896a7 ("powerpc/85xx: Add Quicc Engine support for p1025rdb")
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> 
>   arch/powerpc/platforms/85xx/mpc85xx_rdb.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/powerpc/platforms/85xx/mpc85xx_rdb.c b/arch/powerpc/platforms/85xx/mpc85xx_rdb.c
> index ec9f60fbebc7..e0cec670d8db 100644
> --- a/arch/powerpc/platforms/85xx/mpc85xx_rdb.c
> +++ b/arch/powerpc/platforms/85xx/mpc85xx_rdb.c
> @@ -76,7 +76,7 @@ static void __init mpc85xx_rdb_setup_arch(void)
>   			/* P1025 has pins muxed for QE and other functions. To
>   			* enable QE UEC mode, we need to set bit QE0 for UCC1
>   			* in Eth mode, QE0 and QE3 for UCC5 in Eth mode, QE9
> -			* and QE12 for QE MII management singals in PMUXCR
> +			* and QE12 for QE MII management signals in PMUXCR
>   			* register.
>   			*/
>   				setbits32(&guts->pmuxcr, MPC85xx_PMUXCR_QE(0) |

  reply	other threads:[~2023-11-24 13:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 10:02 [PATCH] powerpc/85xx: Fix typo in code comment Dario Binacchi
2023-11-24 13:08 ` Christophe Leroy [this message]
2023-11-24 13:14   ` Dario Binacchi
2023-12-07 12:38 ` Michael Ellerman

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=4ce802db-b6d0-4eec-9ae2-5383a6f01843@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=b32736@freescale.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=galak@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=oss@buserror.net \
    --cc=pali@kernel.org \
    --cc=robh@kernel.org \
    --cc=timur@freescale.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;
as well as URLs for NNTP newsgroup(s).