Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp811315ybk; Wed, 13 May 2020 13:49:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxVd9Y45BCp0E32nG+uyRzTyJ0QS8f44I/poJyVU69/XI+GyOYvLhPv1myHm8iAqf46XQHp X-Received: by 2002:a17:906:17c1:: with SMTP id u1mr813875eje.47.1589402959889; Wed, 13 May 2020 13:49:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589402959; cv=none; d=google.com; s=arc-20160816; b=ZnTXx7KdpnyBwCoqufcM1vZD02glTMprAblG27VAuKQqXIrq6xIX22cCvThox6XzYY AnmhtprXcE9eWoLBMYaGkDCHfmmz2mI5HDwtA5aC892p4LOlZtoMJAzSoQEaX75KvDaK HQTg4A4+dcpvm+r3A3wWelCsV4s8HWtrcZB5eotYWLiQxRujDOlcv+FZ+y/VGzH8oj7q KOft3+wQBaJ4QmXbzkD/ql0SteH8VDnAD876QS8i2cc/6b9qo6G3jbRxsj36t5iOoDvE 0MNwciDYKHImmxChVTkK/jPO8jM21O4pjEW3y+R1QQ06Mh4USP7TgheVlHKROhmVncUb Q0cQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=PLXZAi37IonIyCzUr9ISl5C6uNqyedns4HHs4rcKjfw=; b=0PBBSoQ9nVTlAuDTGkbWat1yoGeBJwVt0iQcDaPN+qfZ7aJqL3DWyYeoT6O/qCEE8y nifCD+LSGYU6BQATJTzCAhTqXLkxhGtXIU/rty3HNT/tT1llgl3XpG26dlw10wz86RQZ jsEZfVrzjz3F1445/9Jx0hWB/DON+eGxrMqUqZzfgkyJRe0dFTPCL2UruM6zDWhHSzzD t4jxTG+RVlJd3uaEuzFzWOxld3KyfTEZ6dZth/y0uyYwPJgpqoy7c7BMZJtPp2O8vDVX K1cwL2p/YGSEVxFLvzbKUYHwLA1tUBTJyXV9M+OWZPyyKAUqhX8gL1AZwtlCXZFvDrSs Sb2Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p24si401928edi.428.2020.05.13.13.48.57; Wed, 13 May 2020 13:49:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389092AbgEMO7i (ORCPT + 99 others); Wed, 13 May 2020 10:59:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:53646 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728692AbgEMO7h (ORCPT ); Wed, 13 May 2020 10:59:37 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id BD3C1AD5B; Wed, 13 May 2020 14:59:37 +0000 (UTC) Received: by lion.mk-sys.cz (Postfix, from userid 1000) id 68682602FD; Wed, 13 May 2020 16:59:34 +0200 (CEST) Date: Wed, 13 May 2020 16:59:34 +0200 From: Michal Kubecek To: netdev@vger.kernel.org Cc: Andrew Lunn , Russell King - ARM Linux admin , Doug Berger , "David S. Miller" , Florian Fainelli , Heiner Kallweit , bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 1/4] net: ethernet: validate pause autoneg setting Message-ID: <20200513145934.GD9071@lion.mk-sys.cz> References: <1589243050-18217-1-git-send-email-opendmb@gmail.com> <1589243050-18217-2-git-send-email-opendmb@gmail.com> <20200512004714.GD409897@lunn.ch> <20200512185503.GD1551@shell.armlinux.org.uk> <0cf740ed-bd13-89d5-0f36-1e5305210e97@gmail.com> <20200513053405.GE1551@shell.armlinux.org.uk> <20200513092050.GB1605@shell.armlinux.org.uk> <20200513134925.GE499265@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200513134925.GE499265@lunn.ch> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 13, 2020 at 03:49:25PM +0200, Andrew Lunn wrote: > > So, I think consistency of implementation is more important than fixing > > this; the current behaviour has been established for many years now. > > With netlink ethtool we have the possibility of adding a new API to > control this. And we can leave the IOCTL API alone, and the current > ethtool commands. We can add a new command to ethtool which uses the new API. > > Question is, do we want to do this? Would we be introducing yet more > confusion, rather than making the situation better? For the record, netlink interface for pause parameters which is based on existing ioctl and ethtool_ops is in mainline but not in v5.6. If there is a consensus that it should be rethought, it might still be possible to drop these two request types and come with a better API later (i.e. in 5.8 or 5.9 cycle). Michal