From: Zefir Kurtisi <zefir.kurtisi@neratec.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@adurom.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] [trivial] nl80211: fix typos in comments
Date: Mon, 07 May 2012 11:45:11 +0200 [thread overview]
Message-ID: <4FA799A7.9020101@neratec.com> (raw)
In-Reply-To: <1336383672.4325.8.camel@jlt3.sipsolutions.net>
On 05/07/2012 11:41 AM, Johannes Berg wrote:
> On Mon, 2012-05-07 at 12:35 +0300, Kalle Valo wrote:
>> Zefir Kurtisi <zefir.kurtisi@neratec.com> writes:
>>
>>> - * @NL80211_DFS_FCC_: Country follows DFS master rules from FCC
>>> - * @NL80211_DFS_FCC_: Country follows DFS master rules from ETSI
>>> - * @NL80211_DFS_JP_: Country follows DFS master rules from JP/MKK/Telec
>>> + * @NL80211_DFS_FCC: Country follows DFS master rules from FCC
>>> + * @NL80211_DFS_ETSI: Country follows DFS master rules from ETSI
>>> + * @NL80211_DFS_JP: Country follows DFS master rules from JP/MKK/Telec
>>
>> Are there any user space applications which use these enums? If there are,
>> this change will break them which is bad (tm).
>
> No, it actually just fixes kernel-doc .. the constant names are spelled
> wrong in the comment.
>
> johannes
>
Yep, 'trivial' since only C&P typos fixed. Or is there a better tag for
non functional modifications (comments, indentation, etc.)?
next prev parent reply other threads:[~2012-05-07 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 9:21 [PATCH] [trivial] nl80211: fix typos in comments Zefir Kurtisi
2012-05-07 9:35 ` Kalle Valo
2012-05-07 9:41 ` Johannes Berg
2012-05-07 9:45 ` Zefir Kurtisi [this message]
2012-05-07 9:46 ` Kalle Valo
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=4FA799A7.9020101@neratec.com \
--to=zefir.kurtisi@neratec.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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