From: Tom Lendacky <thomas.lendacky@amd.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/8] amd-xgbe: AMD XGBE driver update 2014-07-25
Date: Tue, 29 Jul 2014 08:21:23 -0500 [thread overview]
Message-ID: <53D79FD3.5010407@amd.com> (raw)
In-Reply-To: <20140728.173359.1659401063111761702.davem@davemloft.net>
On 07/28/2014 07:33 PM, David Miller wrote:
> From: Tom Lendacky <thomas.lendacky@amd.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.
>
Will do. I was planning on going through the whole driver and replacing
all the DBGPR type functions in a future patch. For now I'll just
remove them from this patch series and address the rest of the driver
in a future patch.
Thanks,
Tom
prev parent reply other threads:[~2014-07-29 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 21:10 [PATCH net-next 0/8] amd-xgbe: AMD XGBE driver update 2014-07-25 Tom Lendacky
2014-07-25 21:10 ` [PATCH net-next 1/8] amd-xgbe: Add dma-coherent to device bindings documentation Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 2/8] amd-xgbe: Add hardware timestamp support Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 3/8] amd-xgbe: Update/fix 2.5GbE support Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 4/8] amd-xgbe: Base queue fifo size and enablement on ring count Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 5/8] amd-xgbe-phy: Updates to rate change complete check Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 6/8] amd-xgbe-phy: Updates to KR training initiation Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 7/8] amd-xgbe-phy: Print out the auto-negotiation method used Tom Lendacky
2014-07-25 21:11 ` [PATCH net-next 8/8] amd-xgbe: Add traffic class support Tom Lendacky
2014-07-29 0:33 ` [PATCH net-next 0/8] amd-xgbe: AMD XGBE driver update 2014-07-25 David Miller
2014-07-29 13:21 ` Tom Lendacky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53D79FD3.5010407@amd.com \
--to=thomas.lendacky@amd.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).