From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: "'Kees Cook'" <keescook@chromium.org>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Cc: "'Randy Dunlap'" <rdunlap@infradead.org>,
"'Andy Whitcroft'" <apw@canonical.com>,
"'Joe Perches'" <joe@perches.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] scripts/spelling.txt: add "fimware" misspelling
Date: Wed, 27 Apr 2016 12:06:07 +0800 [thread overview]
Message-ID: <004901d1a03a$2066a440$6133ecc0$@cn.fujitsu.com> (raw)
In-Reply-To: <20160426234753.GA20444@www.outflux.net>
Hi, Kees Cook
* From: Kees Cook [mailto:keescook@chromium.org]
> Sent: Wednesday, April 27, 2016 7:48 AM
> To: Andrew Morton <akpm@linux-foundation.org>
> Cc: Randy Dunlap <rdunlap@infradead.org>; Andy Whitcroft
> <apw@canonical.com>; Joe Perches <joe@perches.com>; Zhao Lei
> <zhaolei@cn.fujitsu.com>; linux-doc@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: [PATCH] scripts/spelling.txt: add "fimware" misspelling
>
> A few instances of "fimware" instead of "firmware" were found. Fix these
> and add it to the spelling.txt file.
>
Better to add this change:
# grep fimware * -R
Documentation/firmware_class/README: - kernel searchs the fimware image with name $FIRMWARE directly
Thanks
Zhaolei
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Looks like spelling.txt changes have been going in through -mm?
> ---
> drivers/media/usb/dvb-usb/dib0700_core.c | 2 +-
> drivers/scsi/bfa/bfi.h | 2 +-
> drivers/staging/comedi/drivers/daqboard2000.c | 2 +-
> scripts/spelling.txt | 1 +
> 4 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/usb/dvb-usb/dib0700_core.c
> b/drivers/media/usb/dvb-usb/dib0700_core.c
> index c16f999b9d7c..bf890c3d9cda 100644
> --- a/drivers/media/usb/dvb-usb/dib0700_core.c
> +++ b/drivers/media/usb/dvb-usb/dib0700_core.c
> @@ -517,7 +517,7 @@ int dib0700_download_firmware(struct usb_device
> *udev, const struct firmware *fw
> if (nb_packet_buffer_size < 1)
> nb_packet_buffer_size = 1;
>
> - /* get the fimware version */
> + /* get the firmware version */
> usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
> REQUEST_GET_VERSION,
> USB_TYPE_VENDOR | USB_DIR_IN, 0, 0,
> diff --git a/drivers/scsi/bfa/bfi.h b/drivers/scsi/bfa/bfi.h
> index 97600dcec649..5f698d038b21 100644
> --- a/drivers/scsi/bfa/bfi.h
> +++ b/drivers/scsi/bfa/bfi.h
> @@ -356,7 +356,7 @@ struct bfi_ioc_image_hdr_s {
> u8 port0_mode; /* device mode for port 0 */
> u8 port1_mode; /* device mode for port 1 */
> u32 exec; /* exec vector */
> - u32 bootenv; /* fimware boot env */
> + u32 bootenv; /* firmware boot env */
> u32 rsvd_b[2];
> struct bfi_ioc_fwver_s fwver;
> u32 md5sum[BFI_IOC_MD5SUM_SZ];
> diff --git a/drivers/staging/comedi/drivers/daqboard2000.c
> b/drivers/staging/comedi/drivers/daqboard2000.c
> index 57ab6680e3ae..a536a15c1d30 100644
> --- a/drivers/staging/comedi/drivers/daqboard2000.c
> +++ b/drivers/staging/comedi/drivers/daqboard2000.c
> @@ -26,7 +26,7 @@
> * Much of the functionality of this driver was determined from reading
> * the source code for the Windows driver.
> *
> - * The FPGA on the board requires fimware, which is available from
> + * The FPGA on the board requires firmware, which is available from
> * http://www.comedi.org in the comedi_nonfree_firmware tarball.
> *
> * Configuration options: not applicable, uses PCI auto config
> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
> index 946caf3bd694..fa79c6d2a5b8 100644
> --- a/scripts/spelling.txt
> +++ b/scripts/spelling.txt
> @@ -428,6 +428,7 @@ feautures||features
> fetaure||feature
> fetaures||features
> fileystem||filesystem
> +fimware||firmware
> finanize||finalize
> findn||find
> finilizes||finalizes
> --
> 2.6.3
>
>
> --
> Kees Cook
> Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-04-27 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:47 Kees Cook
2016-04-27 4:06 ` Zhao Lei [this message]
2016-04-27 16:14 ` Kees Cook
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='004901d1a03a$2066a440$6133ecc0$@cn.fujitsu.com' \
--to=zhaolei@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.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®