From: Jiri Slaby <jirislaby@gmail.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: [PATCH 1/1] IWL: fix WARN typo
Date: Mon, 05 Jan 2009 17:04:49 +0100 [thread overview]
Message-ID: <49622FA1.5060603@gmail.com> (raw)
In-Reply-To: <1231171404-22822-1-git-send-email-jirislaby@gmail.com>
On 01/05/2009 05:03 PM, Jiri Slaby wrote:
> new kew -> a new key
...
> - "no space for new kew");
> + "no space for a new key");
There are more of them, hold on, I'll post an updated one.
next prev parent reply other threads:[~2009-01-05 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 16:03 [PATCH 1/1] IWL: fix WARN typo Jiri Slaby
2009-01-05 16:04 ` Jiri Slaby [this message]
2009-01-05 16:06 ` [PATCH 1/1 #2] " Jiri Slaby
2009-01-09 20:18 ` John W. Linville
2009-01-09 21:42 ` John W. Linville
2009-01-09 22:20 ` Johannes Berg
2009-01-05 19:02 ` [PATCH 1/1] " Johannes Berg
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=49622FA1.5060603@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomas.winkler@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).