From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH net] ethtool: do not print warning for applications
 using legacy API
Date: Wed, 3 Jan 2018 07:19:02 -0800
Message-ID: <20180103071902.6280e67e@xeon-e3>
References: <20171229180252.6981-1-sthemmin@microsoft.com>
        <20180102.215002.671661044941618104.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: decot@googlers.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
To: David Miller <davem@davemloft.net>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20180102.215002.671661044941618104.davem@davemloft.net>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

On Tue, 02 Jan 2018 21:50:02 -0500 (EST)
David Miller <davem@davemloft.net> wrote:

> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Fri, 29 Dec 2017 10:02:52 -0800
> 
> > From: Stephen Hemminger <stephen@networkplumber.org>
> > 
> > In kernel log ths message appears on every boot:
> >  "warning: `NetworkChangeNo' uses legacy ethtool link settings API,
> >   link modes are only partially reported"
> > 
> > When ethtool link settings API changed, it started complaining about
> > usages of old API. Ironically, the original patch was from google but
> > the application using the legacy API is chrome.  
> 
> Chrome on my machine doesn't do this, FWIW...

I did report a bug to chrome team as well.