linux-kernel - TI wlxx driver, #define collision for 'QURIKS'

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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAA344TGKAajYm5LxK4Cy=UUcErkaPCq9B=xpNLY5KuPws6p4Rw@mail.gmail.com>
Date:	Thu, 13 Mar 2014 11:17:53 -0700
From:	nat ersoz <natersoz@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: TI wlxx driver, #define collision for 'QURIKS'

Greetings Linux Wifi developers, TI wlxxx specifically.

I noticed a symbol definitions 'collision' in the TI wl12xx device
driver source code.
My working kernel is 3.13.0-rc3, but this is true for 3.14.rc3 as well
as the wireless-next branch.
http://git.kernel.org/cgit/linux/kernel/git/linville/wireless-next.git/

These quirks and conditions may (likely it seems) conflict:

File: linux/include/wl12xx.h:
#define WL12XX_PLATFORM_QUIRK_EDGE_IRQ    BIT(0)

File: drivers/net/wireless/ti/wlcore/wlcore.h
#define WLCORE_QUIRK_END_OF_TRANSACTION        BIT(0)

I think this might be a problem in several scenarios. Thoughts?
Please CC me in replies. I am not subscribed to LKML.
If I'm wasting time or completely off base, please merely reply as
such and I will slink away.

Thanks,

Nat Ersoz
natersoz@...il.com
425-417-5182 (cell)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/