PS: I should really go and read the specs to see if we can steer v4 and v6 independently but my memory says we cannot.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Feed Search
Yesterday
Yesterday
Thu, Jan 22
Thu, Jan 22
Tue, Jan 20
Tue, Jan 20
In D54794#1252564, @adrian wrote:Oh, there's no callers of ieee80211_ampdu_request() outside of net80211? I was worried that the existing AMPDU implementing drivers would hiccup with the return value changing!
Rather than leaving the vlog as a reminder, deal with the TODO comment
in net80211_ic_printf() as well and remove the vlog comment from there.
Update treturn as suggested by @emaste.
I don't get the correlation between your commit message and these changes. Is there an actual change (due to casting) in this change? Or is there a problem "somewhere" but this change does not necessarily address that?
Your first line of commit message is RX repetitive; I assume one should be tx. Should be fixed before commit.
Sun, Jan 18
Sun, Jan 18
Sat, Jan 17
Sat, Jan 17
bz committed rGdd1d6a06542c: net80211: fix arguments to IEEE80211_NOTE in ieee80211_fix_rate (authored by Yichen Chai <yichen.chai@gmail.com>).
bz committed rG2e93d2f39d72: net80211: fix arguments to IEEE80211_NOTE in ieee80211_fix_rate (authored by Yichen Chai <yichen.chai@gmail.com>).
Fri, Jan 16
Fri, Jan 16
bz committed rG6d7d95b4758d: dc(4): fix argument to if_foreach_llmaddr() for 21143. (authored by chrisj_rtems.org).