netdev - Re: [PATCH net-next v2 0/7] amd-xgbe: AMD XGBE driver updates 2015-05-12

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: <20150515.152240.2196567854221782278.davem@davemloft.net>
Date:	Fri, 15 May 2015 15:22:40 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	thomas.lendacky@....com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/7] amd-xgbe: AMD XGBE driver updates
 2015-05-12

From: Tom Lendacky <thomas.lendacky@....com>
Date: Thu, 14 May 2015 11:43:51 -0500

> The following series of patches includes functional updates and changes
> to the driver.
> 
> - Add additional statistics to be collected and reported
> - Use the netif_* functions for issuing some debug and informational
>   driver messages
> - Rx path SKB allocation cleanup/simplification
> - Remove stand-alone phylib driver and incorporate function into the nic
>   driver
> - Simplify device tree support while maintaining backwards compatibility
> - Fix the flow control negotiation logic to properly configure flow
>   control
> - Remove the checking and setting of the device dma_mask field
> 
> This patch series is based on net-next.
> 
> Changes in v2:
> - Change from using the netif_msg_*/netdev_* combination for issuing
>   messages to the more concise netif_*

Series applied, thanks.

But I hope we don't regret this down the road if this PHY actually is
used in some other application in the future and we need to
reinstantiate the phylib driver again.
--
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