Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp7158000imm; Sun, 20 May 2018 20:18:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZqNvBEAZzE9cIHO4dTtFkB91TtA/X+nqnirbu44gqCx5x/OCyRyNoc8uD551P1b+QiiRYQ5 X-Received: by 2002:a65:4d8e:: with SMTP id p14-v6mr8212871pgq.296.1526872736066; Sun, 20 May 2018 20:18:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526872736; cv=none; d=google.com; s=arc-20160816; b=KLtbJbo7tYyRIlx65DMgm5As0YT4TNaMDbtWN3f3xLxyS8rTk/Ls+/gfXG66UTrAJP ds3UMmQnOA4KscO+ai+dyP+Ga8lT7a3p8MqGQ1vi4P1KOQediVqVBqU26T4VMJMIMc89 p4ByMBvCROKGiR0E/oxHu4kOs3iAiu91e6z/xb1lpHfMvLeCWf7/FO1cXscQMZZBG0sz lINNtjo+4oDlCZkZ+DUI9G5x2gL3cBDYNe5DSdNM6pwgNDYjWYqe28Fm84C75FSsTOaN HdXAbBllIbf30fJuj++/L2ugZfN+RI03kUF8aJM30A+M6lYCDZb5oawP2PCeWZcfu9O1 LEhQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=cAw8hAqdYJbQBCN3dmnpHZ6/V/a/7HhfKdqgM6SGzHY=; b=OJiDT21mCDD/YMJZzwysjqaITf/G7Fr1uH0qI0mv1juJq3bDR9l4PzozkNKMc3xIvr GWkmef9YeuV5lcESGNeWMIfGsjeLoDuC+FCnwVPVyUDlFurIQDa2yCKt2FeIUI8jxzcs mHPrVE/xKV3mxfT/CK6lq+pMGdZtEJfhbQldleKzeY4fFKUQcK+A1c9e21uKTM7nC/gj kZoQHEfQ1yWsLGG3FuOHMA0Pfo2SmTlm4wvtJi3//nmpRcDxAIMCKyM+ZFk6Uq16x2cW JpmAKlH3MaLf4gSfHQxzZHeqw2FtHYthAAxmq9ILrvPmv8m3/AEzofsfA8HFoWyoljxv EwWw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l11-v6si10356561pgq.501.2018.05.20.20.18.41; Sun, 20 May 2018 20:18:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752689AbeEUDSZ (ORCPT + 99 others); Sun, 20 May 2018 23:18:25 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:48872 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752357AbeEUDSX (ORCPT ); Sun, 20 May 2018 23:18:23 -0400 Received: from localhost (pool-173-77-163-54.nycmny.fios.verizon.net [173.77.163.54]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id D041213416B97; Sun, 20 May 2018 20:18:22 -0700 (PDT) Date: Sun, 20 May 2018 23:18:20 -0400 (EDT) Message-Id: <20180520.231820.868530785962553925.davem@davemloft.net> To: acelan.kao@canonical.com Cc: jcliburn@gmail.com, chris.snook@gmail.com, rakesh@tuxera.com, netdev@vger.kernel.org, emily.chien@canonical.com, andrew@lunn.ch, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] Revert "alx: remove WoL support" From: David Miller In-Reply-To: References: <20180514032839.32079-1-acelan.kao@canonical.com> <20180514.093504.1396660355199793729.davem@davemloft.net> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sun, 20 May 2018 20:18:23 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: AceLan Kao Date: Mon, 21 May 2018 11:14:00 +0800 > We are willing to fix the issue, but we don't have a machine to > reproduce it, and the WoL feature has been removed 5 years ago, it's > hard to find those buggy machines. Have you bothered to ask the person who did the revert? > WoL is a feature that is only used by a very small group of people, > and the wake up issue looks like only happens on some > platforms. Which means only small part of the group of people are > affected. One of those people was the wireless networking stack maintainer. > So, it's not a serious issue worth to remove it from alx driver. I disagree. You must fix the regression solved by the revert, before adding WoL support back to the driver. I'm not going to say this again. Thank you.