From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Luciano Coelho <coelho@ti.com>
Cc: "trivial@kernel.org" <trivial@kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]drivers:wireless:acx.h change initate to initiate
Date: Fri, 28 Jan 2011 11:56:58 -0800 [thread overview]
Message-ID: <4D431F8A.3000403@gmail.com> (raw)
In-Reply-To: <1296244444.3069.399.camel@pimenta>
On 01/28/11 11:54, Luciano Coelho wrote:
> On Fri, 2011-01-28 at 20:50 +0100, Justin P. Mattock wrote:
>> Not sure if this is a typo or not. if it is then feel free to take this.
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>>
>> ---
>> drivers/net/wireless/wl12xx/acx.h | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/net/wireless/wl12xx/acx.h b/drivers/net/wireless/wl12xx/acx.h
>> index 7bd8e4d..c56088b 100644
>> --- a/drivers/net/wireless/wl12xx/acx.h
>> +++ b/drivers/net/wireless/wl12xx/acx.h
>> @@ -987,7 +987,7 @@ struct wl1271_acx_ht_capabilities {
>> * Note, driver will still leave space for HT control in packets
>> * regardless of the value of this field. FW will be responsible
>> * to drop the HT field from any frame when this Bit set to 0.
>> - * bit 5 - Allow RD initiation in TXOP. FW is allowed to initate RD.
>> + * bit 5 - Allow RD initiation in TXOP. FW is allowed to initiate RD.
>> * Exact policy setting for this feature is TBD.
>> * Note, this bit can only be set to 1 if bit 3 is set to 1.
>> */
>
> Yep, it's a typo. Thanks for fixing it.
>
> Acked-by: Luciano Coelho<coelho@ti.com>
>
alright.. cool..
Justin P. Mattock
next prev parent reply other threads:[~2011-01-28 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 19:50 [PATCH]drivers:wireless:acx.h change initate to initiate Justin P. Mattock
2011-01-28 19:54 ` Luciano Coelho
2011-01-28 19:56 ` Justin P. Mattock [this message]
2011-02-17 15:52 ` 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=4D431F8A.3000403@gmail.com \
--to=justinmattock@gmail.com \
--cc=coelho@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).