From: Ghanshyam Agrawal <ghanshyam1898@gmail.com>
To: mahesh@linux.ibm.com, oohall@gmail.com, mpe@ellerman.id.au,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
aneesh.kumar@kernel.org, naveen.n.rao@linux.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org,
Ghanshyam Agrawal <ghanshyam1898@gmail.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/3] powerpc/eeh: Add full stop to fix a grammatical error
Date: Thu, 28 Dec 2023 15:45:19 +0530 [thread overview]
Message-ID: <5cac0f67a54c21ddadf5f2f844bf85544efecbdb.1703756365.git.ghanshyam1898@gmail.com> (raw)
In-Reply-To: <cover.1703756365.git.ghanshyam1898@gmail.com>
Add a full stop at the end of one of the sentences to fix the
grammatical error.
Suggested-by: Michael Ellerman <mpe@ellerman.id.au>
Signed-off-by: Ghanshyam Agrawal <ghanshyam1898@gmail.com>
---
V2:
Added full stop to fix a grammatical error
V1:
This change was suggested in V1.
arch/powerpc/kernel/eeh_pe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/eeh_pe.c b/arch/powerpc/kernel/eeh_pe.c
index 8e0c1a8b8641..77d05740977a 100644
--- a/arch/powerpc/kernel/eeh_pe.c
+++ b/arch/powerpc/kernel/eeh_pe.c
@@ -27,7 +27,7 @@ static LIST_HEAD(eeh_phb_pe);
* eeh_set_pe_aux_size - Set PE auxiliary data size
* @size: PE auxiliary data size
*
- * Set PE auxiliary data size
+ * Set PE auxiliary data size.
*/
void eeh_set_pe_aux_size(int size)
{
--
2.25.1
next prev parent reply other threads:[~2023-12-28 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 10:15 [PATCH v2 0/3] Fix typos, grammatical errors and add units of function param Ghanshyam Agrawal
2023-12-28 10:15 ` [PATCH v2 1/3] powerpc/eeh: Fix spelling of the word "auxillary" Ghanshyam Agrawal
2023-12-28 10:15 ` Ghanshyam Agrawal [this message]
2023-12-28 10:15 ` [PATCH v2 3/3] powerpc/eeh: Add the units of size param in the description Ghanshyam Agrawal
2024-05-08 13:39 ` [PATCH v2 0/3] Fix typos, grammatical errors and add units of function param 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=5cac0f67a54c21ddadf5f2f844bf85544efecbdb.1703756365.git.ghanshyam1898@gmail.com \
--to=ghanshyam1898@gmail.com \
--cc=aneesh.kumar@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=oohall@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).