From: Hans de Goede <hdegoede@redhat.com>
To: Dipendra Khadka <kdipendra88@gmail.com>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
gregkh@linuxfoundation.org
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] drivers: staging: media: atomisp: pci: Fixes a spelling mistake in sh_css_defs.h
Date: Sun, 31 Dec 2023 10:39:13 +0100 [thread overview]
Message-ID: <b78d7f1d-ced8-42d2-8523-7b26f917d3e9@redhat.com> (raw)
In-Reply-To: <20231218153200.450148-1-kdipendra88@gmail.com>
Hi,
On 12/18/23 16:32, Dipendra Khadka wrote:
> The script checkpatch.pl reported a spelling error
> in sh_css_defs.h as below:
>
> '''
> WARNING: 'upto' may be misspelled - perhaps 'up to'?
> /* The FPGA system (vec_nelems == 16) only supports upto 5MP */
> ^^^^
> '''
>
> This patch corrects a spelling error,
> changing "upto" to "up to".
>
> 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_defs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/media/atomisp/pci/sh_css_defs.h b/drivers/staging/media/atomisp/pci/sh_css_defs.h
> index 7eb10b226f0a..2afde974e75d 100644
> --- a/drivers/staging/media/atomisp/pci/sh_css_defs.h
> +++ b/drivers/staging/media/atomisp/pci/sh_css_defs.h
> @@ -131,7 +131,7 @@ RGB[0,8191],coef[-8192,8191] -> RGB[0,8191]
> * invalid rows/columns that result from filter initialization are skipped. */
> #define SH_CSS_MIN_DVS_ENVELOPE 12U
>
> -/* The FPGA system (vec_nelems == 16) only supports upto 5MP */
> +/* The FPGA system (vec_nelems == 16) only supports up to 5MP */
> #define SH_CSS_MAX_SENSOR_WIDTH 4608
> #define SH_CSS_MAX_SENSOR_HEIGHT 3450
>
prev parent reply other threads:[~2023-12-31 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 15:32 [PATCH] drivers: staging: media: atomisp: pci: Fixes a spelling mistake in sh_css_defs.h Dipendra Khadka
2023-12-31 9:39 ` 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=b78d7f1d-ced8-42d2-8523-7b26f917d3e9@redhat.com \
--to=hdegoede@redhat.com \
--cc=gregkh@linuxfoundation.org \
--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 NNTP newsgroup(s).