From: <linux@martijnvandeventer.nl>
To: "'Jerome Brunet'" <jbrunet@baylibre.com>
Cc: "'Neil Armstrong'" <neil.armstrong@linaro.org>,
"'Michael Turquette'" <mturquette@baylibre.com>,
"'Stephen Boyd'" <sboyd@kernel.org>,
"'Kevin Hilman'" <khilman@baylibre.com>,
"'Martin Blumenstingl'" <martin.blumenstingl@googlemail.com>,
<linux-amlogic@lists.infradead.org>, <linux-clk@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] clk: meson: g12a: Fix kernel warnings when no display attached
Date: Thu, 6 Mar 2025 21:13:27 +0100 [thread overview]
Message-ID: <001401db8ed4$392ef030$ab8cd090$@martijnvandeventer.nl> (raw)
In-Reply-To: <1j4j065avo.fsf@starbuckisacylon.baylibre.com>
Hi Jerome,
>
> Once again, you are encouraged to fix things up ... where fixes are needed.
Encouragement is not the problem, time is ;-)
> DRM is hardly immutable. If you don't feel like you can do it on your own,
> you can still engage with the other contributors who may know this
> better and help you.
Maybe in a few months when I have some more time. Thanks.
> >
> > On the other hand, I also understand that if you, as a maintainer, allow
> > that, chances are it will never see a proper fix. :-)
> >
> > Cheers!
> >
--
Best regards,
Martijn
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-03-06 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 22:17 [PATCH] clk: meson: g12a: Fix kernel warnings when no display attached Martijn van Deventer
2025-02-14 9:08 ` Jerome Brunet
2025-02-26 20:39 ` linux
2025-02-27 9:38 ` Jerome Brunet
2025-03-06 16:48 ` linux
2025-03-06 17:26 ` Jerome Brunet
2025-03-06 20:13 ` linux [this message]
2025-02-14 11:15 ` 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='001401db8ed4$392ef030$ab8cd090$@martijnvandeventer.nl' \
--to=linux@martijnvandeventer.nl \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=sboyd@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