From: Jiri Slaby <jirislaby@kernel.org>
To: Yinchuan Guo <guoych37@mail2.sysu.edu.cn>, linux-kernel@vger.kernel.org
Cc: lee.jones@linaro.org, james.smart@broadcom.com,
dick.kennedy@broadcom.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, gregkh@linuxfoundation.org,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH] Subject: [PATCH] sound: drivers: fix typo 'reguest' to 'request'
Date: Mon, 12 Feb 2024 07:07:58 +0100 [thread overview]
Message-ID: <360ef165-2ee3-4018-9b24-e77cd82f3417@kernel.org> (raw)
In-Reply-To: <20240211182846.3608447-1-guoych37@mail2.sysu.edu.cn>
Hi,
the subject is mangled.
On 11. 02. 24, 19:28, Yinchuan Guo wrote:
> This patch fixes a widespread spelling mistake of the word "request"
> (incorrectly spelled as "reguest") across multiple files.
>
> Signed-off-by: Yinchuan Guo <guoych37@mail2.sysu.edu.cn>
> ---
> drivers/mfd/da9063-irq.c | 2 +-
> drivers/scsi/lpfc/lpfc_sli.c | 2 +-
> drivers/tty/serial/max310x.c | 2 +-
> drivers/tty/serial/sccnxp.c | 2 +-
These do not look like "sound". You should send/fix them separately.
> sound/soc/codecs/rt274.c | 2 +-
> sound/soc/codecs/rt286.c | 2 +-
> sound/soc/codecs/rt298.c | 2 +-
> sound/soc/codecs/rt5514-spi.c | 2 +-
> sound/soc/codecs/rt5640.c | 2 +-
> sound/soc/codecs/rt5645.c | 2 +-
> sound/soc/codecs/rt5651.c | 2 +-
> sound/soc/codecs/rt5659.c | 2 +-
> sound/soc/codecs/rt5663.c | 2 +-
> sound/soc/codecs/rt5665.c | 2 +-
> sound/soc/codecs/rt5668.c | 2 +-
> sound/soc/codecs/rt5682-i2c.c | 2 +-
thanks,
--
js
suse labs
prev parent reply other threads:[~2024-02-12 6:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 18:28 [PATCH] Subject: [PATCH] sound: drivers: fix typo 'reguest' to 'request' Yinchuan Guo
2024-02-11 21:04 ` Greg KH
2024-02-12 6:07 ` Jiri Slaby [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=360ef165-2ee3-4018-9b24-e77cd82f3417@kernel.org \
--to=jirislaby@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dick.kennedy@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=guoych37@mail2.sysu.edu.cn \
--cc=james.smart@broadcom.com \
--cc=jejb@linux.ibm.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.