From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/asm: Fix a typo
Date: Mon, 22 Mar 2021 11:45:10 -0700 [thread overview]
Message-ID: <96eda8ce-1d89-1491-51a2-92ba9883912b@infradead.org> (raw)
In-Reply-To: <20210322113254.2081445-1-unixbhaskar@gmail.com>
On 3/22/21 4:32 AM, Bhaskar Chowdhury wrote:
>
> s/poiner/pointer/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
However, it would be a GOOD THING to collect multiple similar
patches that are in e.g. arch/powerpc/ and send them as one patch
instead of many little patches.
> ---
> arch/powerpc/include/asm/cpm2.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/include/asm/cpm2.h b/arch/powerpc/include/asm/cpm2.h
> index 2211b934ecb4..bda45788cfcc 100644
> --- a/arch/powerpc/include/asm/cpm2.h
> +++ b/arch/powerpc/include/asm/cpm2.h
> @@ -594,7 +594,7 @@ typedef struct fcc_enet {
> uint fen_p256c; /* Total packets 256 < bytes <= 511 */
> uint fen_p512c; /* Total packets 512 < bytes <= 1023 */
> uint fen_p1024c; /* Total packets 1024 < bytes <= 1518 */
> - uint fen_cambuf; /* Internal CAM buffer poiner */
> + uint fen_cambuf; /* Internal CAM buffer pointer */
> ushort fen_rfthr; /* Received frames threshold */
> ushort fen_rfcnt; /* Received frames count */
> } fcc_enet_t;
> --
--
~Randy
next prev parent reply other threads:[~2021-03-22 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 11:32 [PATCH] powerpc/asm: Fix a typo Bhaskar Chowdhury
2021-03-22 18:45 ` Randy Dunlap [this message]
2021-03-22 23:48 ` 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=96eda8ce-1d89-1491-51a2-92ba9883912b@infradead.org \
--to=rdunlap@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=unixbhaskar@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;
as well as URLs for NNTP newsgroup(s).