From: Maha Maryam Javaid <mahamaryamjavaid@gmail.com>
To: andy@kernel.org, hansg@kernel.org, mchehab@kernel.org
Cc: sakari.ailus@linux.intel.com, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Maha Maryam Javaid <mahamaryamjavaid@gmail.com>
Subject: [PATCH] staging: media: ia_css_event_public: fix typo in ia_css_event_public.h
Date: Wed, 29 Apr 2026 14:05:30 -0400 [thread overview]
Message-ID: <20260429180530.6944-1-mahamaryamjavaid@gmail.com> (raw)
Fix spelling mistake: Therefor ==> Therefore
Signed-off-by: Maha Maryam Javaid <mahamaryamjavaid@gmail.com>
---
drivers/staging/media/atomisp/pci/ia_css_event_public.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/pci/ia_css_event_public.h b/drivers/staging/media/atomisp/pci/ia_css_event_public.h
index f7215dd96739..8eec3b0af65e 100644
--- a/drivers/staging/media/atomisp/pci/ia_css_event_public.h
+++ b/drivers/staging/media/atomisp/pci/ia_css_event_public.h
@@ -110,7 +110,7 @@ struct ia_css_event {
until IA_CSS_MAX_EXPOSURE_ID is reached, after that they wrap
around to IA_CSS_MIN_EXPOSURE_ID again.
Note that in case frames are dropped, this will not be reflected
- in the exposure IDs. Therefor applications should not use this
+ in the exposure IDs. Therefore applications should not use this
to detect frame drops. */
u32 fw_handle;
/** Firmware Handle for ACC_STAGE_COMPLETE event (not valid for other
--
2.34.1
next reply other threads:[~2026-04-29 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 18:05 Maha Maryam Javaid [this message]
2026-04-29 18:32 ` [PATCH] staging: media: ia_css_event_public: fix typo in ia_css_event_public.h Andy Shevchenko
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=20260429180530.6944-1-mahamaryamjavaid@gmail.com \
--to=mahamaryamjavaid@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--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