From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Daniel Golle <daniel@makrotopia.org>,
frank-w@public-files.de, Frank Wunderlich <linux@fw-web.de>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: [PATCH] arm64: dts: mt7622: fix switch probe on bananapi-r64
Date: Mon, 1 Jul 2024 11:15:45 +0300 [thread overview]
Message-ID: <aeb255ff-3755-4f76-a8f8-cda27a67f818@arinc9.com> (raw)
In-Reply-To: <130518e2-d6dd-49ed-9cc2-ca9cdec93b98@leemhuis.info>
On 01/07/2024 11:04, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 01.07.24 09:44, Arınç ÜNAL wrote:
>> On 01/07/2024 09:16, Linux regression tracking (Thorsten Leemhuis) wrote:
>>> [CCing the other net maintainers]
>>>
>>> On 25.06.24 10:51, AngeloGioacchino Del Regno wrote:
>>>> Il 25/06/24 07:56, Linux regression tracking (Thorsten Leemhuis) ha
>>>> scritto:
>>>>> On 17.06.24 13:08, Arınç ÜNAL wrote:
>>>>>> On 17/06/2024 11:33, Linux regression tracking (Thorsten Leemhuis)
>>>>>> wrote:
>>>>>> [...]
>>>>> It looks more and more like we are stuck here (or was there progress
>>>>> and
>>>>> I just missed it?) while the 6.10 final is slowly getting closer.
>>>>> Hence:
>>>>>
>>>>> AngeloGioacchino, should we ask the net maintainers to revert
>>>>> 868ff5f4944aa9 ("net: dsa: mt7530-mdio: read PHY address of switch from
>>>>> device tree") for now to resolve this regression? Reminder, there is
>>>>> nothing wrong with that commit per se afaik, it just exposes a problem
>>>>> that needs to be fixed first before it can be reapplied.
>>>>
>>>> To be clear on this: I asked for the commit to be fixed such that it
>>>> guarantees
>>>> backwards compatibility with older device trees.
>>>>
>>>> If no fix comes,
>>>
>>> I haven't see any since that mail, did you? If not, I think...
>>>
>>>> then I guess that we should ask them to revert this commit
>>>> until a fix is available.
>>>
>>> ...it's time to ask them for the revert to resolve this for -rc7 (and
>>> avoid a last minute revert), or what do you think?
>>
>> This is quite frustrating. I absolutely won't consent to a revert. [...]
>
> Reminder: try to not see a revert as a bad thing. It's just means "not
> ready yet, revert and we'll try again later" -- that's actually
> something Linus wrote just a few hours ago:
> https://lore.kernel.org/lkml/CAHk-=wgQMOscLeeA3QXOs97xOz_CTxdqJjpC20tJ-7bUdHWtSA@mail.gmail.com/
Except it is ready and trying again is my responsibility, which means
unnecessary work for me to do. I've already got a ton of things to do.
Applying the device tree patch resolves this regression; no reverts needed.
And then there's the patch in the works by Daniel that will address all the
remaining cases outside of the reported regression.
Arınç
next prev parent reply other threads:[~2024-07-01 8:16 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 20:48 [PATCH] arm64: dts: mt7622: fix switch probe on bananapi-r64 Frank Wunderlich
2024-05-17 2:17 ` Arınç ÜNAL
2024-05-17 6:27 ` Frank Wunderlich
2024-05-23 10:44 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-31 5:40 ` Thorsten Leemhuis
2024-05-31 6:10 ` Arınç ÜNAL
2024-06-06 8:26 ` Thorsten Leemhuis
2024-06-06 9:01 ` Arınç ÜNAL
2024-06-06 9:34 ` Thorsten Leemhuis
2024-06-07 14:03 ` Paolo Abeni
2024-06-07 14:15 ` Thorsten Leemhuis
2024-06-11 11:30 ` Thorsten Leemhuis
2024-06-11 11:38 ` Arınç ÜNAL
2024-06-11 12:28 ` AngeloGioacchino Del Regno
2024-06-11 12:56 ` Arınç ÜNAL
2024-06-11 13:03 ` AngeloGioacchino Del Regno
2024-06-11 18:15 ` Arınç ÜNAL
2024-06-17 8:33 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-17 11:08 ` Arınç ÜNAL
2024-06-25 5:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-25 6:17 ` Arınç ÜNAL
2024-06-25 6:57 ` Linux regression tracking (Thorsten Leemhuis)
2024-06-25 8:17 ` Arınç ÜNAL
2024-06-25 8:49 ` AngeloGioacchino Del Regno
2024-06-26 3:07 ` Arınç ÜNAL
2024-06-25 8:51 ` AngeloGioacchino Del Regno
2024-07-01 6:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-07-01 7:02 ` Aw: " Frank Wunderlich
2024-07-01 7:44 ` Arınç ÜNAL
2024-07-01 8:04 ` Linux regression tracking (Thorsten Leemhuis)
2024-07-01 8:15 ` Arınç ÜNAL [this message]
2024-07-30 9:41 ` AngeloGioacchino Del Regno
2024-07-30 11:22 ` arinc.unal
2024-07-30 11:38 ` arinc.unal
2024-07-30 16:04 ` Krzysztof Kozlowski
2024-07-30 16:22 ` Daniel Golle
2024-07-30 16:38 ` Arınç ÜNAL
2024-07-31 5:29 ` Krzysztof Kozlowski
2024-07-31 7:55 ` Arınç ÜNAL
2024-05-31 6:12 ` Arınç ÜNAL
2024-05-31 6:18 ` Frank Wunderlich
2024-05-31 6:27 ` Arınç ÜNAL
2024-05-17 13:17 ` Rob Herring (Arm)
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=aeb255ff-3755-4f76-a8f8-cda27a67f818@arinc9.com \
--to=arinc.unal@arinc9.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
/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