From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 35375C77B72 for ; Fri, 14 Apr 2023 14:09:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230236AbjDNOJY (ORCPT ); Fri, 14 Apr 2023 10:09:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60810 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230220AbjDNOJU (ORCPT ); Fri, 14 Apr 2023 10:09:20 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BE8A9B759 for ; Fri, 14 Apr 2023 07:08:44 -0700 (PDT) Received: from [192.168.1.137] (unknown [213.194.153.37]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: rcn) by madras.collabora.co.uk (Postfix) with ESMTPSA id 6AAB8660321F; Fri, 14 Apr 2023 15:08:28 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1681481309; bh=I+aHzA+Q4ne4xfBmJkGe2Y0X33bIvFmF69y9bnWuVcQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Fi2ZjYIAcu7jqxL95ctMMCV4n/D+ocJfsLyTMmwc/3arbxRYiga0wltghFMnIjanD 6zh2URKn/GWRn5DdqXtXGg9RkQX3hC3l2HUFOg4pstgQCjmwkyswc8E/zdyjdTUkWP QY74JSdTyMG2ihTL02ADdN5+R2A9FQ1DJy9Y8F5dYqNnwk5QGXADF2xQmZ1ierLhW3 oUPhnSIvT3kDYJFis5yeBa/rIaJaZLsm/IZut1esgQHaLBeEVqQrH02TB8Tj9XSUyq dxTTbptKkKtd6nSuXQ+u7BUKyHv+byhvzxdbF7vpzdqgaXbi38lHr0gmKWGWly6SRH cTKaxd/HzRlTQ== Message-ID: <569c0f2f-ff7b-9367-e33e-ddf37a13232b@collabora.com> Date: Fri, 14 Apr 2023 16:08:25 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH net] bgmac: fix *initial* chip reset to support BCM5358 Content-Language: en-US To: Linux regressions mailing list , Florian Fainelli , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Arnd Bergmann , netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, Jon Mason References: <20230227091156.19509-1-zajec5@gmail.com> <20230404134613.wtikjp6v63isofoc@rcn-XPS-13-9305> <002c1f96-b82f-6be7-2530-68c5ae1d962d@milecki.pl> From: =?UTF-8?Q?Ricardo_Ca=c3=b1uelo?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi Thorsten, On 14/4/23 16:04, Linux regression tracking (Thorsten Leemhuis) wrote: > What happened to this? It seems there wasn't any progress since above > mail week. But well, seems to be a odd issue anyway (is that one of > those issues that CI systems find, but don't cause practical issues in > the field?). Hence: can somebody with more knowledge about this please > tell if it this is something I can likely drop from the list of tacked > regressions? From Rafał's answer, I think we can consider this a false positive and move on. Cheers, Ricardo