From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: 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,
Sasha Levin <sashal@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH 1/3] ARM: dts: meson: Fix the UART compatible strings
Date: Mon, 10 Apr 2023 08:09:54 +0200 [thread overview]
Message-ID: <d7f389ab-914b-c48e-dc8e-290fb72f345e@collabora.com> (raw)
In-Reply-To: <2023040604-washtub-undivided-5763@gregkh>
Thanks Thorsten and Greg,
I sent the original report to stable@vger.kernel.org. Sorry for
the confusion, I'm still learning about how report regressions
properly using regzbot, specially for stable branches. Thorsten's
guidelines are being very helpful here.
Cheers,
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-10 6:11 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
2023-04-06 9:06 ` Thorsten Leemhuis
2023-04-06 9:14 ` Greg KH
2023-04-10 6:09 ` Ricardo Cañuelo [this message]
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=d7f389ab-914b-c48e-dc8e-290fb72f345e@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.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 \
--cc=sashal@kernel.org \
--cc=stable@vger.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