From: Greg KH <gregkh@linuxfoundation.org>
To: "Everest K.C." <everestkc@everestkc.com.np>
Cc: u.kleine-koenig@pengutronix.de, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Fix spelling errors in file drivers/usb/gadget/udc/m66592-udc.c
Date: Mon, 16 Sep 2024 08:52:16 +0200 [thread overview]
Message-ID: <2024091639-tasty-relay-5082@gregkh> (raw)
In-Reply-To: <20240916052357.6487-1-everestkc@everestkc.com.np>
On Sun, Sep 15, 2024 at 11:23:56PM -0600, Everest K.C. wrote:
> Fixed spelling errors in error message and comments that
> were reported by codespell as follows:
> unexpect --> unexpected
> workaound --> workaround
>
> Signed-off-by: Everest K.C. <everestkc@everestkc.com.np>
> ---
> v1 --> v2: Removed the coding style fix. This patch now only
> fixes spelling errors. The coding style will be fixed
> in a separate patch.
>
> drivers/usb/gadget/udc/m66592-udc.c | 18 +++++++++---------
If you do:
git log --oneline drivers/usb/gadget/udc/m66592-udc.c
you will see the format for how to properly write the Subject: line
here.
As this is your first kernel contributions, I recommend working in an
area that is designed for new developers to help work through these
types of issues, drivers/staging/ Get some experience there before
moving out into other areas of the kernel. Also note that many
subsystems do not care about things like spelling fixes, so be careful.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-16 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 1:45 [PATCH] Fix spelling errors and codestyle in file drivers/usb/gadget/udc/m66592-udc.c Everest K.C.
2024-09-16 4:10 ` Greg KH
2024-09-16 5:23 ` [PATCH v2] Fix spelling errors " Everest K.C.
2024-09-16 6:52 ` Greg KH [this message]
2024-09-16 7:35 ` Everest K.C.
2024-09-16 7:40 ` Greg KH
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=2024091639-tasty-relay-5082@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=everestkc@everestkc.com.np \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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