From: Greg KH <greg@kroah.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: "Alex Lanzano" <lanzano.alex@gmail.com>,
"Mehdi Djait" <mehdi.djait@bootlin.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
"Conor Dooley" <conor+dt@kernel.org>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Christophe Jaillet" <christophe.jaillet@wanadoo.fr>,
"Shuah Khan" <skhan@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Subject: Re: [PATCH v9 0/2] Add driver for Sharp Memory LCD
Date: Mon, 7 Oct 2024 11:53:45 +0200 [thread overview]
Message-ID: <2024100737-audacious-subplot-7f4a@gregkh> (raw)
In-Reply-To: <4e1d50de-8e00-47a3-94e0-5ee9c5df8755@web.de>
On Mon, Oct 07, 2024 at 11:34:13AM +0200, Markus Elfring wrote:
> > This patch series add support for the monochrome Sharp Memory LCD panels.
> …
> > ---
> > Changes in v9:
> …
>
> Would you like to benefit from the application of scope-based resource management
> (also for this software component)?
Hi,
This is the semi-friendly patch-bot of Greg Kroah-Hartman.
Markus, you seem to have sent a nonsensical or otherwise pointless
review comment to a patch submission on a Linux kernel developer mailing
list. I strongly suggest that you not do this anymore. Please do not
bother developers who are actively working to produce patches and
features with comments that, in the end, are a waste of time.
Patch submitter, please ignore Markus's suggestion; you do not need to
follow it at all. The person/bot/AI that sent it is being ignored by
almost all Linux kernel maintainers for having a persistent pattern of
behavior of producing distracting and pointless commentary, and
inability to adapt to feedback. Please feel free to also ignore emails
from them.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2024-10-07 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 1:30 [PATCH v9 0/2] Add driver for Sharp Memory LCD Alex Lanzano
2024-10-07 1:30 ` [PATCH v9 1/2] dt-bindings: display: Add Sharp Memory LCD bindings Alex Lanzano
2024-10-07 1:30 ` [PATCH v9 2/2] drm/tiny: Add driver for Sharp Memory LCD Alex Lanzano
2024-10-07 7:40 ` Uwe Kleine-König
2024-10-07 9:34 ` [PATCH v9 0/2] " Markus Elfring
2024-10-07 9:53 ` Greg KH [this message]
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=2024100737-audacious-subplot-7f4a@gregkh \
--to=greg@kroah.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzk+dt@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mehdi.djait@bootlin.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tzimmermann@suse.de \
--cc=u.kleine-koenig@baylibre.com \
--cc=ukleinek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.