linux-kernel - Re: [PATCH v3 net-next 0/4] Further fix for dsa unbinding

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

Message-ID: <5665EE7E.9020600@gmail.com>
Date:	Mon, 07 Dec 2015 12:39:26 -0800
From:	Florian Fainelli <f.fainelli@...il.com>
To:	Neil Armstrong <narmstrong@...libre.com>, davem@...emloft.net,
	andrew@...n.ch, linux@...ck-us.net,
	vivien.didelot@...oirfairelinux.com, fabf@...net.be,
	pavel.nakonechny@...tlab.ru, joe@...ches.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 net-next 0/4] Further fix for dsa unbinding

On 07/12/15 04:57, Neil Armstrong wrote:
> This serie fixes further issues for DSA dynamic unbinding.
> The first patch completely removes the PHY link state polling.
> The two following cleans up the dsa state upon removal.
> The last patch moves slave destroy code as slave function and
> adds missing netdev and phy cleanup calls.
> 
> v1: http://lkml.kernel.org/r/562F8ECB.6050709@baylibre.com
> v2: http://lkml.kernel.org/r/56321D9A.8010109@baylibre.com
> remove phy fix and add missing calls in dsa_switch_destroy
> then add dedicated dsa_slave_destroy
> 
> v3: remove polling instead of fixing it, make single patch for
> dsa slave destroy
> 
> Neil Armstrong (4):
>   net: dsa: remove DSA link polling
>   net: dsa: cleanup resources upon module removal
>   net: dsa: Add missing master netdev dev_put() calls
>   net: dsa: move dsa slave destroy code to slave.c

Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
-- 
Florian
--
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/