From: "Winkler, Tomas" <tomas.winkler@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: RE: [PATCH] mei: fix spellos
Date: Wed, 13 Dec 2023 07:09:15 +0000 [thread overview]
Message-ID: <MN2PR11MB40936BB0DF3B1AAA66C01AA3E58DA@MN2PR11MB4093.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20231213044158.4449-1-rdunlap@infradead.org>
> Correct spellos reported by codespell.
Can please specify in the commit message that only include/uapi/linux/mei.h is fixed.
Thanks
Tomas
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Tomas Winkler <tomas.winkler@intel.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> include/uapi/linux/mei.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff -- a/include/uapi/linux/mei.h b/include/uapi/linux/mei.h
> --- a/include/uapi/linux/mei.h
> +++ b/include/uapi/linux/mei.h
> @@ -100,14 +100,14 @@ struct mei_connect_client_data_vtag {
> * a FW client on a tagged channel. From this point on, every read
> * and write will communicate with the associated FW client
> * on the tagged channel.
> - * Upone close() the communication is terminated.
> + * Upon close() the communication is terminated.
> *
> * The IOCTL argument is a struct with a union that contains
> * the input parameter and the output parameter for this IOCTL.
> *
> * The input parameter is UUID of the FW Client, a vtag [0,255].
> * The output parameter is the properties of the FW client
> - * (FW protocool version and max message size).
> + * (FW protocol version and max message size).
> *
> * Clients that do not support tagged connection
> * will respond with -EOPNOTSUPP.
prev parent reply other threads:[~2023-12-13 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 4:41 Randy Dunlap
2023-12-13 7:09 ` Winkler, Tomas [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=MN2PR11MB40936BB0DF3B1AAA66C01AA3E58DA@MN2PR11MB4093.namprd11.prod.outlook.com \
--to=tomas.winkler@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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®