Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp207561ybb; Fri, 3 Apr 2020 00:54:10 -0700 (PDT) X-Google-Smtp-Source: APiQypLKY5REU/zhJzuv/Lc1Q73TrMP77dOfcZF+QB+I+R1bJFz8dH2gJ6tPPpWKdga8xpxOsV/H X-Received: by 2002:a05:6830:1ac1:: with SMTP id r1mr5680481otc.139.1585900450562; Fri, 03 Apr 2020 00:54:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585900450; cv=none; d=google.com; s=arc-20160816; b=P8tLKmNN11aNDK7rCPRWyKE66cp4F6RuhtzMPzg04yFJ84IfCVButtsR1CzA2kKDM8 hbtKi5KwwAT0+bkgN2pgMxPkoFMrZ5G++yEw+hGBTKfFm3HKps2Vt+F+I/Kwku9S2nZ4 zagunHXgD/d5gQ0c8D2zdSkneNTcQVAL77oMDoceTkRvVbSD7WGVX2gGWpsWaNOQ9WgH Tr8cScyBwyxNiRbHg+XTZEodApB/ylFBQZaL6hAT3ca2hE2m2LGk3UW1qwTucJzmzofz VgXs71uk0G15HCgKlorDJxbN8aiYzEjK5yVnibybe7/lAHBFV+oH7+NbM18wKrP2xd2/ oXFg== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject; bh=szNOe95hM3UvMyNZ9XNCk2XrN0rchCuAktMFnePqF00=; b=jJMjbLzhXrbF/PvAkV3apQw5l2g1qNq0jB+12J53KIi4ib9TQe9u88xLRCca3rZOai PLj6tVJZ2jItFpDVhwhvm341YukRYgQUmYnSpJE5z4+HJLUclJkuCE7Fgx524bdSb2aG W6FjyzKCF8pO4R6MiTYhmZC9eXigS7JsVbMuvARHDj5K45Bf/S1zEFBpKz8/7LR7r5o0 yhBVVdT+7adccW4sJRQA2jCdJeub+fwf1ylI73ZVYLPGTnzliGcQZjp37gFPqU1BrgDI gFebdPbeH8dc9DxdQ6mh5hbizR/IKds2xofCyL4LQEvffx+Pm76jaT5jb7fDSxbouRJ6 YJTg== 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 p187si3463078oop.28.2020.04.03.00.53.58; Fri, 03 Apr 2020 00:54:10 -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 S2389517AbgDCHha (ORCPT + 99 others); Fri, 3 Apr 2020 03:37:30 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:39897 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730759AbgDCHha (ORCPT ); Fri, 3 Apr 2020 03:37:30 -0400 Received: from [192.168.1.6] (x590ea470.dyn.telefonica.de [89.14.164.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id C112C206442DE; Fri, 3 Apr 2020 09:37:26 +0200 (CEST) Subject: Re: [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME un-configure ULP mode To: Aaron Ma , Hans de Goede , Jeff Kirsher , davem@davemloft.net, intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, sasha.neftin@intel.com References: <20200323191639.48826-1-aaron.ma@canonical.com> <4f9f1ad0-e66a-d3c8-b152-209e9595e5d7@redhat.com> <1c0e602f-1fe7-62b1-2283-b98783782e87@canonical.com> From: Paul Menzel Message-ID: <2d7c1890-9cd8-8134-af12-5c55cd7e1a8e@molgen.mpg.de> Date: Fri, 3 Apr 2020 09:37:26 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <1c0e602f-1fe7-62b1-2283-b98783782e87@canonical.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Linux folks, Am 03.04.20 um 05:15 schrieb Aaron Ma: > I have received the email that you apply this patch to next-queue branch > dev-queue. > > But after this branch is rebased to v5.6, I can't find it. > > Will you apply again? I really urge you to write more elaborate commit messages. The exact error is not listed. The known regressed devices are not listed, so possible testers cannot easily test or affected people cannot find it, when searching the Linux git history. How did you find out, that ME takes more than two seconds? Also, it’s not clear, what effect increasing the timeout has. Does the whole resume process take longer or just getting the Ethernet device back up? Lastly, in case of the timeout, an error message should be printed, so people with even more broken ME devices, get a clue. Without this information, how can anybody know, if this is the right fix and distributions, if it should be backported? Kind regards, Paul