From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>,
"Rafał Miłecki" <zajec5@gmail.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Arnd Bergmann <arnd@arndb.de>,
netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
Jon Mason <jdmason@kudzu.us>
Subject: Re: [PATCH net] bgmac: fix *initial* chip reset to support BCM5358
Date: Fri, 14 Apr 2023 16:08:25 +0200 [thread overview]
Message-ID: <569c0f2f-ff7b-9367-e33e-ddf37a13232b@collabora.com> (raw)
In-Reply-To: <d6990d00-6fd5-cd89-755d-d7f566c574fa@leemhuis.info>
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
next prev parent reply other threads:[~2023-04-14 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 9:11 [PATCH net] bgmac: fix *initial* chip reset to support BCM5358 Rafał Miłecki
2023-02-27 9:54 ` Leon Romanovsky
2023-02-27 18:23 ` Florian Fainelli
2023-02-28 10:30 ` patchwork-bot+netdevbpf
2023-04-04 13:46 ` Ricardo Cañuelo
2023-04-04 13:52 ` Rafał Miłecki
2023-04-05 12:42 ` Florian Fainelli
2023-04-14 14:04 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-14 14:08 ` Ricardo Cañuelo [this message]
2023-04-14 14:12 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-04-05 11:16 ` Linux regression tracking #update (Thorsten Leemhuis)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569c0f2f-ff7b-9367-e33e-ddf37a13232b@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jdmason@kudzu.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafal@milecki.pl \
--cc=regressions@lists.linux.dev \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).