[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140728.173359.1659401063111761702.davem@davemloft.net>
Date: Mon, 28 Jul 2014 17:33:59 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: thomas.lendacky@....com
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/8] amd-xgbe: AMD XGBE driver update
2014-07-25
From: Tom Lendacky <thomas.lendacky@....com>
Date: Fri, 25 Jul 2014 16:10:52 -0500
> This patch series is dependent on the following patch that was
> applied to the net tree and needs to be applied to the net-next
> tree:
> 332cfc823d18 - amd-xgbe: Fix error return code in xgbe_probe()
>
> The following series of patches includes fixes and new support in the
> driver.
>
> - Device bindings documentation update
> - Hardware timestamp support
> - 2.5GbE support changes
> - Fifo sizes based on active queues/rings
> - Phylib driver updates for:
> - Rate change completion check
> - KR training initiation
> - Auto-negotiation results
> - Traffic class support, including DCB support
>
> This patch series is based on net-next.
I was going to apply this, but I couldn't let those function tracing debug
giblets into the tree.
Please remove all of that DBGPR(...., __func__) stuff.
We have a generic function tracer which can be used to trace any path
of execution in the kernel.
--
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
Powered by blists - more mailing lists