From: Hans de Goede <hdegoede@redhat.com>
To: Dipendra Khadka <kdipendra88@gmail.com>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
gregkh@linuxfoundation.org, hpa@redhat.com
Cc: linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] staging: media/atomisp/pci: Fix spelling mistakes in sh_css_mipi.c
Date: Sun, 31 Dec 2023 10:49:34 +0100 [thread overview]
Message-ID: <da90dec8-b0f3-4ebd-92fc-a33ec96b4905@redhat.com> (raw)
In-Reply-To: <20231223064152.79712-1-kdipendra88@gmail.com>
Hi,
On 12/23/23 07:41, Dipendra Khadka wrote:
> codespell reported following spelling mistake
> in sh_css_mipi.c as below:
>
> '''
> ./sh_css_mipi.c:177: separatelly ==> separately
> ./sh_css_mipi.c:540: ofset ==> offset, of set
> '''
> This patch fixes these spelling mistakes by changing
> "separatelly" to "separately" and "ofset" to "offset".
>
> Signed-off-by: Dipendra Khadka <kdipendra88@gmail.com>
Thank you for your patch.
I have merged this in my media-atomisp branch:
https://git.kernel.org/pub/scm/linux/kernel/git/hansg/linux.git/log/?h=media-atomisp
And this patch will be included in my next
pull-request to Mauro (to media subsystem maintainer)
Regards,
Hans
> ---
> drivers/staging/media/atomisp/pci/sh_css_mipi.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/sh_css_mipi.c b/drivers/staging/media/atomisp/pci/sh_css_mipi.c
> index b7c1e164ee24..6e11fd771938 100644
> --- a/drivers/staging/media/atomisp/pci/sh_css_mipi.c
> +++ b/drivers/staging/media/atomisp/pci/sh_css_mipi.c
> @@ -174,7 +174,7 @@ ia_css_mipi_frame_calculate_size(const unsigned int width,
> mem_words = ((embedded_data_size_words + 7) >> 3) +
> mem_words_for_first_line +
> (((height + 1) >> 1) - 1) * mem_words_per_odd_line +
> - /* ceil (height/2) - 1 (first line is calculated separatelly) */
> + /* ceil (height/2) - 1 (first line is calculated separately) */
> (height >> 1) * mem_words_per_even_line + /* floor(height/2) */
> mem_words_for_EOF;
>
> @@ -537,7 +537,7 @@ send_mipi_frames(struct ia_css_pipe *pipe)
>
> /* Hand-over the SP-internal mipi buffers */
> for (i = 0; i < my_css.num_mipi_frames[port]; i++) {
> - /* Need to include the ofset for port. */
> + /* Need to include the offset for port. */
> sh_css_update_host2sp_mipi_frame(port * NUM_MIPI_FRAMES_PER_STREAM + i,
> my_css.mipi_frames[port][i]);
> sh_css_update_host2sp_mipi_metadata(port * NUM_MIPI_FRAMES_PER_STREAM + i,
prev parent reply other threads:[~2023-12-31 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 6:41 [PATCH] staging: media/atomisp/pci: Fix spelling mistakes in sh_css_mipi.c Dipendra Khadka
2023-12-31 9:49 ` Hans de Goede [this message]
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=da90dec8-b0f3-4ebd-92fc-a33ec96b4905@redhat.com \
--to=hdegoede@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@redhat.com \
--cc=kdipendra88@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).