lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 15 Jan 2020 13:55:38 +0000
From:   Jérôme Pouiller <Jerome.Pouiller@...abs.com>
To:     "devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
        "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Kalle Valo <kvalo@...eaurora.org>,
        "David S . Miller" <davem@...emloft.net>,
        Jérôme Pouiller <Jerome.Pouiller@...abs.com>
Subject: [PATCH v2 65/65] staging: wfx: update TODO

From: Jérôme Pouiller <jerome.pouiller@...abs.com>

Some work has been done :)

Signed-off-by: Jérôme Pouiller <jerome.pouiller@...abs.com>
---
 drivers/staging/wfx/TODO | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/drivers/staging/wfx/TODO b/drivers/staging/wfx/TODO
index 6b1cdd24afc9..efcb7c6a5aa7 100644
--- a/drivers/staging/wfx/TODO
+++ b/drivers/staging/wfx/TODO
@@ -1,18 +1,8 @@
 This is a list of things that need to be done to get this driver out of the
 staging directory.
 
-  - Allocation of "link ids" is too complex. Allocation/release of link ids from
-    sta_add()/sta_remove() should be sufficient.
-
-  - The path for packets with IEEE80211_TX_CTL_SEND_AFTER_DTIM flags should be
-    cleaned up. Currently, the process involve multiple work structs and a
-    timer. It could be simplifed. In add, the requeue mechanism triggers more
-    frequently than it should.
-
   - All structures defined in hif_api_*.h are intended to sent/received to/from
-    hardware. All their members whould be declared __le32 or __le16. These
-    structs should only been used in files named hif_* (and maybe in data_*.c).
-    The upper layers (sta.c, scan.c etc...) should manage mac80211 structures.
+    hardware. All their members whould be declared __le32 or __le16.
     See:
        https://lore.kernel.org/lkml/20191111202852.GX26530@ZenIV.linux.org.uk
 
-- 
2.25.0

Powered by blists - more mailing lists