netdev - Re: [PATCH V2 1/2] brcm80211: use container_of to resolve brcms_phy from brcms_phy

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2023667085.710256.1411806144444.open-xchange@webmail.nmp.skynet.be>
Date:	Sat, 27 Sep 2014 10:22:24 +0200 (CEST)
From:	Fabian Frederick <fabf@...net.be>
To:	"John W. Linville" <linville@...driver.com>
Cc:	linux-wireless@...r.kernel.org,
	Arend van Spriel <arend@...adcom.com>,
	Hante Meuleman <meuleman@...adcom.com>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Franky (Zhenhui) Lin" <frankyl@...adcom.com>,
	brcm80211-dev-list@...adcom.com, brudley@...adcom.com
Subject: Re: [PATCH V2 1/2] brcm80211: use container_of to resolve brcms_phy
 from brcms_phy_pub



> On 26 September 2014 at 19:46 "John W. Linville" <linville@...driver.com>
> wrote:
>
>
> These two patches don't seem to apply on wireless-next, and I don't
> have time at the moment to fix them up.  Feel free to repost...

Hello John,

        No problem, you already pushed the 2 same patches from the first (too
generic) patchset

        First patchset for drivers/net (see patch 3 and 4)
        http://marc.info/?l=linux-kernel&m=141064073901334&w=2
       
        No updates in V2 anyway:
        ("V2: 2 separate patches for brcm80211")

Wireless-next commits:
a38a9ef1c064
("brcm80211: use container_of to resolve dma_info from dma_pub")

d68e9f5d8549
("brcm80211: use container_of to resolve brcms_phy from brcms_phy_pub")

Regards,
Fabian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html