From: Dipendra Khadka <kdipendra88@gmail.com>
To: hdegoede@redhat.com, mchehab@kernel.org,
sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org,
hpa@redhat.com
Cc: Dipendra Khadka <kdipendra88@gmail.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH] staging: media: atomisp: pci: Fix spelling mistake in ia_css_acc_types.h
Date: Fri, 22 Dec 2023 20:03:50 +0000 [thread overview]
Message-ID: <20231222200350.2024-1-kdipendra88@gmail.com> (raw)
The script checkpatch.pl reported a spelling error
in ia_css_acc_types.h as below:
'''
WARNING: 'cummulative' may be misspelled - perhaps 'cumulative'?
u32 padding_size; /** total cummulative of bytes added due to section alignment */
^^^^^^^^^^^
'''
This patch corrects a spelling error,
changing "cummulative" to "cumulative".
Signed-off-by: Dipendra Khadka <kdipendra88@gmail.com>
---
drivers/staging/media/atomisp/pci/ia_css_acc_types.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/pci/ia_css_acc_types.h b/drivers/staging/media/atomisp/pci/ia_css_acc_types.h
index d6e52b4971d6..ac6fb0eb990a 100644
--- a/drivers/staging/media/atomisp/pci/ia_css_acc_types.h
+++ b/drivers/staging/media/atomisp/pci/ia_css_acc_types.h
@@ -84,7 +84,7 @@ struct ia_css_blob_info {
memory_offsets; /** offset wrt hdr in bytes */
u32 prog_name_offset; /** offset wrt hdr in bytes */
u32 size; /** Size of blob */
- u32 padding_size; /** total cummulative of bytes added due to section alignment */
+ u32 padding_size; /** total cumulative of bytes added due to section alignment */
u32 icache_source; /** Position of icache in blob */
u32 icache_size; /** Size of icache section */
u32 icache_padding;/** bytes added due to icache section alignment */
--
2.34.1
next reply other threads:[~2023-12-22 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 20:03 Dipendra Khadka [this message]
2023-12-22 20:12 ` Randy Dunlap
2023-12-22 20:29 ` Dipendra Khadka
2023-12-22 20:31 ` Randy Dunlap
2023-12-22 20:34 ` Dipendra Khadka
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=20231222200350.2024-1-kdipendra88@gmail.com \
--to=kdipendra88@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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®