From: Nick Andrew <nick@nick-andrew.net>
To: Trivial Kernel Patches <trivial@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [TRIVIAL PATCH 11/11] Fix misspelling of "firmware" in docs for ncr53c8xx/sym53c8xx
Date: Sat, 03 Jan 2009 19:00:37 +1100 [thread overview]
Message-ID: <20090103080026.27466.25064.stgit@marcab.local> (raw)
In-Reply-To: <20090103074923.27466.7287.stgit@marcab.local>
Fix misspelling of "firmware" in docs for ncr53c8xx/sym53c8xx
It's spelled "firmware".
Signed-off-by: Nick Andrew <nick@nick-andrew.net>
---
Documentation/scsi/ChangeLog.ncr53c8xx | 2 +-
Documentation/scsi/ChangeLog.sym53c8xx | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/scsi/ChangeLog.ncr53c8xx b/Documentation/scsi/ChangeLog.ncr53c8xx
index a9f721a..8b278c1 100644
--- a/Documentation/scsi/ChangeLog.ncr53c8xx
+++ b/Documentation/scsi/ChangeLog.ncr53c8xx
@@ -19,7 +19,7 @@ Sun Sep 24 21:30 2000 Gerard Roudier (groudier@club-internet.fr)
Wed Jul 26 23:30 2000 Gerard Roudier (groudier@club-internet.fr)
* version ncr53c8xx-3.4.1
- - Provide OpenFirmare path through the proc FS on PPC.
+ - Provide OpenFirmware path through the proc FS on PPC.
- Remove trailing argument #2 from a couple of #undefs.
Sun Jul 09 16:30 2000 Gerard Roudier (groudier@club-internet.fr)
diff --git a/Documentation/scsi/ChangeLog.sym53c8xx b/Documentation/scsi/ChangeLog.sym53c8xx
index ef985ec..02ffbc1 100644
--- a/Documentation/scsi/ChangeLog.sym53c8xx
+++ b/Documentation/scsi/ChangeLog.sym53c8xx
@@ -81,7 +81,7 @@ Sun Sep 24 21:30 2000 Gerard Roudier (groudier@club-internet.fr)
Wed Jul 26 23:30 2000 Gerard Roudier (groudier@club-internet.fr)
* version sym53c8xx-1.7.1
- - Provide OpenFirmare path through the proc FS on PPC.
+ - Provide OpenFirmware path through the proc FS on PPC.
- Download of on-chip SRAM using memcpy_toio() doesn't work
on PPC. Restore previous method (MEMORY MOVE from SCRIPTS).
- Remove trailing argument #2 from a couple of #undefs.
next prev parent reply other threads:[~2009-01-03 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 7:49 [TRIVIAL PATCH 00/11] Fix misspelling of "firmware" Nick Andrew
2009-01-03 7:50 ` [TRIVIAL PATCH 01/11] Fix misspelled firmware in Kconfig Nick Andrew
2009-01-03 7:51 ` [TRIVIAL PATCH 02/11] Fix misspelling of "firmware" in atmel.c Nick Andrew
2009-01-03 7:52 ` [TRIVIAL PATCH 03/11] Fix misspelling of "firmware" in ipw2100.c Nick Andrew
2009-01-03 7:53 ` [TRIVIAL PATCH 04/11] Fix misspelling of "firmware" in acpi_memhotplug.c Nick Andrew
2009-01-03 7:54 ` [TRIVIAL PATCH 05/11] Fix misspelling of "firmware" in ql4_mbx.c Nick Andrew
2009-01-03 7:55 ` [TRIVIAL PATCH 06/11] Fix misspelling of "firmware" in megaraid.c Nick Andrew
2009-01-03 7:56 ` [TRIVIAL PATCH 07/11] Fix misspelling of "firmware" in a100u2w.c Nick Andrew
2009-01-03 7:57 ` [TRIVIAL PATCH 08/11] Fix misspelling of "firmware" in qla1280.c Nick Andrew
2009-01-03 7:58 ` [TRIVIAL PATCH 09/11] Fix misspelling of "firmware" in usb.c Nick Andrew
2009-01-03 7:59 ` [TRIVIAL PATCH 10/11] Fix misspelling of "firmware" in powerpc Makefile Nick Andrew
2009-01-03 8:00 ` Nick Andrew [this message]
2009-01-03 23:23 ` [TRIVIAL PATCH 00/11] Fix misspelling of "firmware" Jiri Kosina
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=20090103080026.27466.25064.stgit@marcab.local \
--to=nick@nick-andrew.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@kernel.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