From: Hans de Goede <hdegoede@redhat.com>
To: Roshan Khatri <topofeverest8848@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
Subject: Re: [PATCH] staging: atomisp: Fix spelling mistake in sh_css_internal.h
Date: Tue, 2 Jul 2024 12:41:09 +0200 [thread overview]
Message-ID: <d240c315-b438-462c-90a6-22f7e39b2a7a@redhat.com> (raw)
In-Reply-To: <20240501162620.86865-1-topofeverest8848@gmail.com>
Hi,
On 5/1/24 6:26 PM, Roshan Khatri wrote:
> codespell reported misspelled words still and member.
> This patch fixes misspellings.
>
> Signed-off-by: Roshan Khatri <topofeverest8848@gmail.com>
Thank you for your 5 patches.
I have merged all 5 in my media-atomisp branch:
https://git.kernel.org/pub/scm/linux/kernel/git/hansg/linux.git/log/?h=media-atomisp
And these will be included in my next pull-request to
Mauro (to media subsystem maintainer)
Regards,
Hans
> ---
> drivers/staging/media/atomisp/pci/sh_css_internal.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/sh_css_internal.h b/drivers/staging/media/atomisp/pci/sh_css_internal.h
> index 2349eb4d3767..5395be1ed26b 100644
> --- a/drivers/staging/media/atomisp/pci/sh_css_internal.h
> +++ b/drivers/staging/media/atomisp/pci/sh_css_internal.h
> @@ -509,7 +509,7 @@ struct sh_css_sp_pipeline {
> * of the associated pipe. Dynamic means that the data address can
> * change with every (frame) iteration of the associated pipe
> *
> - * s3a and dis are now also dynamic but (stil) handled separately
> + * s3a and dis are now also dynamic but (still) handled separately
> */
> #define SH_CSS_NUM_DYNAMIC_FRAME_IDS (3)
>
> @@ -597,7 +597,7 @@ struct sh_css_sp_stage {
>
> /*
> * Time: 2012-07-19, 17:40.
> - * Note: Add a new data memeber "debug" in "sh_css_sp_group". This
> + * Note: Add a new data member "debug" in "sh_css_sp_group". This
> * data member is used to pass the debugging command from the
> * Host to the SP.
> *
prev parent reply other threads:[~2024-07-02 10:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 16:26 Roshan Khatri
2024-07-02 10:41 ` 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=d240c315-b438-462c-90a6-22f7e39b2a7a@redhat.com \
--to=hdegoede@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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 \
--cc=topofeverest8848@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
all inboxes | Powered by JetHome®