From: Florian Fainelli <f.fainelli@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
davem@davemloft.net, Joe Perches <josephx.perches@intel.com>
Cc: Shannon Nelson <shannon.nelson@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next v2 01/11] i40e: only warn once of PTP nonsupport in 100Mbit speed
Date: Tue, 18 Nov 2014 10:24:01 -0800 [thread overview]
Message-ID: <546B8EC1.3050407@gmail.com> (raw)
In-Reply-To: <1416303220.2295.19.camel@jtkirshe-mobl>
On 11/18/2014 01:33 AM, Jeff Kirsher wrote:
> On Tue, 2014-11-18 at 01:25 -0800, Jeff Kirsher wrote:
>> From: Shannon Nelson <shannon.nelson@intel.com>
>>
>> Only warn once that PTP is not supported when linked at 100Mbit.
>>
>> Yes, using a static this way means that this once-only message is not
>> port specific, but once only for the life of the driver, regardless of
>> the number of ports. That should be plenty.
>>
>> Change-ID: Ie6476530056df408452e195ef06afd4f57caa4b2
>> Signed-off-by: Shannon Nelson <shannon.nelson@intel.com>
>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
>> ---
>> drivers/net/ethernet/intel/i40e/i40e_ptp.c | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> Florian/Joe-
>
> Since your patch to update the dev_level_once() function is going
> through Greg KH's tree, we will stick with this patch until it gets
> accepted and merged into Dave's tree. Then we will provide a patch to
> update the driver.
Sounds absolutely reasonable to me.
>
>>
>> diff --git a/drivers/net/ethernet/intel/i40e/i40e_ptp.c b/drivers/net/ethernet/intel/i40e/i40e_ptp.c
>> index 537b621..f9151037 100644
>> --- a/drivers/net/ethernet/intel/i40e/i40e_ptp.c
>> +++ b/drivers/net/ethernet/intel/i40e/i40e_ptp.c
>> @@ -382,11 +382,17 @@ void i40e_ptp_set_increment(struct i40e_pf *pf)
>> incval = I40E_PTP_1GB_INCVAL;
>> break;
>> case I40E_LINK_SPEED_100MB:
>> - dev_warn(&pf->pdev->dev,
>> - "%s: 1588 functionality is not supported at 100 Mbps. Stopping the PHC.\n",
>> - __func__);
>> + {
>> + static int warn_once;
>> +
>> + if (!warn_once) {
>> + dev_warn(&pf->pdev->dev,
>> + "1588 functionality is not supported at 100 Mbps. Stopping the PHC.\n");
>> + warn_once++;
>> + }
>> incval = 0;
>> break;
>> + }
>> case I40E_LINK_SPEED_40GB:
>> default:
>> incval = I40E_PTP_40GB_INCVAL;
>
next prev parent reply other threads:[~2014-11-18 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 9:25 [net-next v2 00/11][pull request] Intel Wired LAN Driver Updates 2014-11-18 Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 01/11] i40e: only warn once of PTP nonsupport in 100Mbit speed Jeff Kirsher
2014-11-18 9:33 ` Jeff Kirsher
2014-11-18 18:24 ` Florian Fainelli [this message]
2014-11-18 9:25 ` [net-next v2 02/11] i40e: re-enable VFLR interrupt sooner Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 03/11] i40e: Bump version to 1.1.23 Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 04/11] i40e: Resume Port Tx after DCB event Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 05/11] i40e: Add support to firmware CEE DCBX mode Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 06/11] i40e: Check for LLDP AdminStatus before querying DCBX Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 07/11] i40e: Update VEB's enabled_tc after reconfiguration Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 08/11] i40e: Modify Tx disable wait flow in case of DCB reconfiguration Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 09/11] i40e: Do not disable/enable FCoE VSI with DCB reconfig Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 10/11] i40e: Prevent link flow control settings when PFC is enabled Jeff Kirsher
2014-11-18 9:25 ` [net-next v2 11/11] i40e: Set XPS bit mask to zero in DCB mode Jeff Kirsher
2014-11-18 18:38 ` [net-next v2 00/11][pull request] Intel Wired LAN Driver Updates 2014-11-18 David Miller
2014-11-18 21:45 ` Jeff Kirsher
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=546B8EC1.3050407@gmail.com \
--to=f.fainelli@gmail.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=josephx.perches@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@redhat.com \
--cc=shannon.nelson@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.