From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] ARM: dts: meson: Fix the UART compatible strings
Date: Thu, 6 Apr 2023 10:27:51 +0200 [thread overview]
Message-ID: <44556911-e56e-6171-07dd-05cc0e30c732@collabora.com> (raw)
In-Reply-To: <fdffc009-47cf-e88d-5b9e-d6301f7f73f2@leemhuis.info>
Hi,
On 5/4/23 19:14, Thorsten Leemhuis wrote:
> Wait, what? A patch (5225e1b87432 ("ARM: dts: meson: Fix the UART
> compatible strings")) that was merged for v5.17-rc4 and is not in the
> list of patches that were in 4.14.312-rc1
> (https://lore.kernel.org/all/20230403140351.636471867@linuxfoundation.org/
> ) is meant to suddenly cause this? How is this possible? Am I totally on
> the wrong track here and misunderstanding something, or is this a
> bisection that went horribly sideways?
I didn't say this was introduced in 4.14.312-rc1, this has been failing
for a long time and it was merged for 4.14.267: https://lwn.net/Articles/884977/
Sorry I wasn't clear before.
Regards,
Ricardo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-04-06 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 18:00 [PATCH 0/3] ARM: dts: meson: fix UART device-tree schema validation Martin Blumenstingl
2021-12-27 18:00 ` [PATCH 1/3] ARM: dts: meson: Fix the UART compatible strings Martin Blumenstingl
2023-04-05 13:29 ` Ricardo Cañuelo
2023-04-05 17:14 ` Thorsten Leemhuis
2023-04-06 8:27 ` Ricardo Cañuelo [this message]
2023-04-06 9:06 ` Thorsten Leemhuis
2023-04-06 9:14 ` Greg KH
2023-04-10 6:09 ` Ricardo Cañuelo
2023-04-11 16:53 ` Linux regression tracking (Thorsten Leemhuis)
2021-12-27 18:00 ` [PATCH 2/3] ARM: dts: meson8: Fix the UART device-tree schema validation Martin Blumenstingl
2021-12-27 18:00 ` [PATCH 3/3] ARM: dts: meson8b: " Martin Blumenstingl
2021-12-31 15:38 ` [PATCH 0/3] ARM: dts: meson: fix " Martin Blumenstingl
2022-01-03 14:43 ` Neil Armstrong
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=44556911-e56e-6171-07dd-05cc0e30c732@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=regressions@leemhuis.info \
/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