From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] mac80211: fix more kernel-doc warnings
Date: Wed, 30 Jul 2008 08:46:17 +0200 [thread overview]
Message-ID: <1217400377.10489.79.camel@johannes.berg> (raw)
In-Reply-To: <20080729205916.c4c6c363.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On Tue, 2008-07-29 at 20:59 -0700, Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Fix several kernel-doc warnings in mac80211 header files:
>
> Warning(linux-2.6.27-rc1//include/net/mac80211.h:759): Enum value
> 'IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE' not described in enum
> 'ieee80211_hw_flags'
Thanks. That one, however, is already gone now, I had merely forgotten
to remove the flag completely.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-07-30 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 3:59 [PATCH] mac80211: fix more kernel-doc warnings Randy Dunlap
2008-07-30 6:46 ` Johannes Berg [this message]
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=1217400377.10489.79.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.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