public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tarkan Erimer <tarkan.erimer@turknet.net.tr>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>, Nick Andrew <nick@nick-andrew.net>,
	Trivial Kernel Patches <trivial@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL PATCH 00/20] Fix misspelling of "firmware"
Date: Tue, 27 Jan 2009 09:49:34 +0200	[thread overview]
Message-ID: <497EBC8E.4040607@turknet.net.tr> (raw)
In-Reply-To: <3f9a31f40901262235k1c1fec76q41fb007f6e7cb22f@mail.gmail.com>

Jaswinder Singh Rajput wrote:
> I send post to your original thread and also also CC to concern persons.
>
> --
> JSR
>   
Thanks. I already replied it.

Tarkan ERIMER

  reply	other threads:[~2009-01-27  7:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  1:59 [TRIVIAL PATCH 00/20] Fix misspelling of "firmware" Nick Andrew
2009-01-26  1:59 ` [TRIVIAL PATCH 01/20] Fix misspelling of "firmware" in ia64-kvm.txt Nick Andrew
2009-01-26  2:00 ` [TRIVIAL PATCH 02/20] Fix misspelling of "firmware" in firmware.txt Nick Andrew
2009-01-26  2:00 ` [TRIVIAL PATCH 03/20] Fix misspelling of "firmware" in ip27-smp.c Nick Andrew
2009-01-26  2:01 ` [TRIVIAL PATCH 04/20] Fix misspelling of firmware in thinkpad_acpi.c Nick Andrew
2009-01-26  2:02 ` [TRIVIAL PATCH 05/20] Fix misspelling of firmware in sb1250-mac.c Nick Andrew
2009-01-26  2:02 ` [TRIVIAL PATCH 06/20] Fix misspelling of firmware in tg3.c Nick Andrew
2009-01-26  2:03 ` [TRIVIAL PATCH 07/20] Fix misspelling of firmware in ipw2100.c Nick Andrew
2009-01-26  2:03 ` [TRIVIAL PATCH 08/20] Fix misspelling of firmware in ipw2200.c Nick Andrew
2009-01-26  2:04 ` [TRIVIAL PATCH 09/20] Fix misspelling of firmware in cmd.c Nick Andrew
2009-01-26  2:04 ` [TRIVIAL PATCH 10/20] Fix misspelling of firmware in pci.c Nick Andrew
2009-01-26  2:05 ` [TRIVIAL PATCH 11/20] Fix misspelling of firmware in ueagle-atm.c Nick Andrew
2009-01-26  2:05 ` [TRIVIAL PATCH 12/20] Fix misspelling of firmware in ChangeLog.history Nick Andrew
2009-01-26  2:06 ` [TRIVIAL PATCH 13/20] Fix misspelling of firmware in libata.h Nick Andrew
2009-01-26  2:06 ` [TRIVIAL PATCH 14/20] Fix misspelling of firmware in disk.c Nick Andrew
2009-01-26  2:07 ` [TRIVIAL PATCH 15/20] Fix misspelling of firmware in pss.c Nick Andrew
2009-01-26  2:07 ` [TRIVIAL PATCH 16/20] Fix misspelling of firmware in aica.c Nick Andrew
2009-01-26  2:08 ` [TRIVIAL PATCH 17/20] Fix misspelling of firmware in head_64.S Nick Andrew
2009-01-26  2:08 ` [TRIVIAL PATCH 18/20] Fix misspelling of firmware in hpmain.c Nick Andrew
2009-01-26  2:09 ` [TRIVIAL PATCH 19/20] Fix misspelling of firmware in iwl3945-base.c Nick Andrew
2009-01-26  2:09 ` [TRIVIAL PATCH 20/20] Fix misspelling of firmware in iwl-agn.c Nick Andrew
2009-01-26  4:08 ` [TRIVIAL PATCH 00/20] Fix misspelling of "firmware" Alexey Dobriyan
2009-01-26 10:00 ` Jiri Kosina
2009-01-26 14:39   ` Tarkan Erimer
2009-01-26 17:07     ` Jiri Kosina
2009-01-27  7:39       ` Tarkan Erimer
2009-01-27  6:35     ` Jaswinder Singh Rajput
2009-01-27  7:49       ` Tarkan Erimer [this message]
2009-01-27  7:40   ` Nick Andrew

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=497EBC8E.4040607@turknet.net.tr \
    --to=tarkan.erimer@turknet.net.tr \
    --cc=jaswinderlinux@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@nick-andrew.net \
    --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