public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 00/11] Fix misspelling of "firmware"
Date: Sat, 03 Jan 2009 18:49:33 +1100	[thread overview]
Message-ID: <20090103074923.27466.7287.stgit@marcab.local> (raw)

Fix misspellings of "firmware" which I noticed in 2.6.28. All are comment
changes except for the change to drivers/scsi/qla4xxx/ql4_mbx.c which
is in a string argument to dev_info().

Nick.
---

Nick Andrew (11):
      Fix misspelling of "firmware" in docs for ncr53c8xx/sym53c8xx
      Fix misspelling of "firmware" in powerpc Makefile
      Fix misspelling of "firmware" in usb.c
      Fix misspelling of "firmware" in qla1280.c
      Fix misspelling of "firmware" in a100u2w.c
      Fix misspelling of "firmware" in megaraid.c
      Fix misspelling of "firmware" in ql4_mbx.c
      Fix misspelling of "firmware" in acpi_memhotplug.c
      Fix misspelling of "firmware" in ipw2100.c
      Fix misspelling of "firmware" in atmel.c
      Fix misspelled firmware in Kconfig


 Documentation/scsi/ChangeLog.ncr53c8xx |    2 +-
 Documentation/scsi/ChangeLog.sym53c8xx |    2 +-
 arch/powerpc/boot/Makefile             |    2 +-
 drivers/acpi/acpi_memhotplug.c         |    2 +-
 drivers/base/Kconfig                   |    2 +-
 drivers/net/wireless/atmel.c           |    2 +-
 drivers/net/wireless/ipw2100.c         |    2 +-
 drivers/scsi/a100u2w.c                 |    2 +-
 drivers/scsi/megaraid.c                |    4 ++--
 drivers/scsi/qla1280.c                 |    4 ++--
 drivers/scsi/qla4xxx/ql4_mbx.c         |    2 +-
 drivers/uwb/i1480/dfu/usb.c            |    2 +-
 12 files changed, 14 insertions(+), 14 deletions(-)

-- 
PGP Key ID = 0x418487E7                      http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A  67E3 6266 6EB9 4184 87E7

             reply	other threads:[~2009-01-03  7:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03  7:49 Nick Andrew [this message]
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 ` [TRIVIAL PATCH 11/11] Fix misspelling of "firmware" in docs for ncr53c8xx/sym53c8xx Nick Andrew
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=20090103074923.27466.7287.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