[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YCZSTJuDiPGaQ1yV@kroah.com>
Date: Fri, 12 Feb 2021 11:02:52 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Pritthijit Nath <pritthijit.nath@...oud.com>
Cc: vireshk@...nel.org, johan@...nel.org, elder@...nel.org,
devel@...verdev.osuosl.org, greybus-dev@...ts.linaro.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] staging: greybus: Fixed a misspelling in hid.c
On Fri, Feb 12, 2021 at 03:20:08PM +0530, Pritthijit Nath wrote:
> Fixed the spelling of 'transfered' to 'transferred'.
>
> Signed-off-by: Pritthijit Nath <pritthijit.nath@...oud.com>
> ---
> Fixed the typo in the patch which was meant to fix that very typo.
> Really sorry for last time.
> Hope this does not have any other typo.
>
> drivers/staging/greybus/hid.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/greybus/hid.c b/drivers/staging/greybus/hid.c
> index a56c3fb5d35a..adb91286803a 100644
> --- a/drivers/staging/greybus/hid.c
> +++ b/drivers/staging/greybus/hid.c
> @@ -254,7 +254,7 @@ static int __gb_hid_output_raw_report(struct hid_device *hid, __u8 *buf,
>
> ret = gb_hid_set_report(ghid, report_type, report_id, buf, len);
> if (report_id && ret >= 0)
> - ret++; /* add report_id to the number of transfered bytes */
> + ret++; /* add report_id to the number of transferred bytes */
>
> return 0;
> }
> --
> 2.25.1
>
> _______________________________________________
> devel mailing list
> devel@...uxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version,
or properly version the subject line of your patch. Please read the
section entitled "The canonical patch format" in the kernel file,
Documentation/SubmittingPatches for what needs to be done here to
properly describe this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists