netdev - Re: [PATCH net-next] net: phy: export phy_suspend and 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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAGVrzcYkswjw+kd3A3BJxXeyeUHvr4D+Ud7btNnJ=SRwP5AppA@mail.gmail.com>
Date:	Tue, 8 Jul 2014 20:59:47 -0700
From:	Florian Fainelli <f.fainelli@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev <netdev@...r.kernel.org>,
	Vince Bridgers <vbridgers2013@...il.com>
Subject: Re: [PATCH net-next] net: phy: export phy_suspend and phy_resume

2014-07-08 20:37 GMT-07:00 David Miller <davem@...emloft.net>:
> From: Florian Fainelli <f.fainelli@...il.com>
> Date: Tue,  8 Jul 2014 10:38:36 -0700
>
>> phy_suspend and phy_resume are two commonly used helper functions that
>> need to be exported for Ethernet drivers to be built as modules
>>
>> Fixes: 40755a0fce17 ("net: systemport: add suspend and resume support")
>> Signed-off-by: Florian Fainelli <f.fainelli@...il.com>
>
> First of all, the commit in question went into 'net' not 'net-next'.

I am confused now, because I sent the patches against net-next and
still see them in your net-next tree here:

https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=40755a0fce17c39557fd55b634024082671074ed

>
> Second of all, I reverted it.

I remember you replied to Vince about his patches which also depended
on phy_suspend/resume to be there and you did revert his changes.

>
> So this patch is not appropriate unless/until that commit gets
> re-added, and it's not targetted at the proper tree anyways.
-- 
Florian
--
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