From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] d80211: Add API to generate RTS and CTS-to-self frames
Date: Mon, 5 Feb 2007 14:53:57 +0100 [thread overview]
Message-ID: <200702051453.57919.mb@bu3sch.de> (raw)
In-Reply-To: <1170682980.3572.16.camel@johannes.berg>
On Monday 05 February 2007 14:43, Johannes Berg wrote:
> On Mon, 2007-02-05 at 14:12 +0100, Michael Buesch wrote:
>
> > - u16 rts_cts_duration; /* duration field for RTS/CTS frame */
>
> I'd think this was here for a purpose. Maybe some hardware generates the
> frame but not the duration field?
>
> Then again, if that's the case we can always export the functions to
> calculate it as library functions.
Only rt2x00 used it to generate an rts frame with it own custom
generation function. So after switching to the d80211 RTS API
it's unneeded now.
If some driver needs the duration field in future, we should
simply export ieee80211_rts_duration().
--
Greetings Michael.
next prev parent reply other threads:[~2007-02-05 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 13:12 [PATCH] d80211: Add API to generate RTS and CTS-to-self frames Michael Buesch
2007-02-05 13:14 ` [PATCH] bcm43xx-d80211: Use d80211 API to generate RTS/CTS frames Michael Buesch
2007-02-05 13:15 ` [PATCH] rt2x00-d80211: " Michael Buesch
2007-02-05 13:31 ` [PATCH] d80211: Add API to generate RTS and CTS-to-self frames Michael Buesch
2007-02-05 13:43 ` Johannes Berg
2007-02-05 13:53 ` Michael Buesch [this message]
2007-02-05 14:58 ` Jouni Malinen
2007-02-05 15:28 ` Michael Buesch
2007-02-05 16:47 ` Jouni Malinen
2007-02-05 16:53 ` Michael Buesch
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=200702051453.57919.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--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;
as well as URLs for NNTP newsgroup(s).