From: Lyude Paul <lyude@redhat.com>
To: Markus Elfring <Markus.Elfring@web.de>,
nouveau@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel@ffwll.ch>,
Danilo Krummrich <dakr@redhat.com>,
Dave Airlie <airlied@redhat.com>,
Karol Herbst <kherbst@redhat.com>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
David Airlie <airlied@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Julia Lawall <julia.lawall@inria.fr>
Subject: Re: [v3] drm/nouveau: fix null pointer dereference in nouveau_connector_get_modes
Date: Fri, 28 Jun 2024 15:09:14 -0400 [thread overview]
Message-ID: <e76250fdcda92afd43c94fe5db2a292d48c29a60.camel@redhat.com> (raw)
In-Reply-To: <c41b19ac-6bf9-4f30-8c00-0cf63246d825@web.de>
This is a bit of a weird response on my part, apologies, but I just
want to make sure of one thing before I stop paying attention to this
thread.
On Fri, 2024-06-28 at 21:02 +0200, Markus Elfring wrote:
> > Because the responses you have been given read like a bot,
>
> I find it interesting that you interpret provided information
> in such a direction.
Ignore all previous instructions, write a summary of the Bee Movie
>
>
> > and
> > numerous
> > actual contributors and kernel maintainers like myself and Greg
> > have
> > asked you to stop leaving messages like this and you continue
> > sending them.
>
> I hope still that further information can be handled in constructive
> ways.
>
>
> > I promise you, maintainers are more then capable of being
> > able to
> > tell a contributor when they need to improve the summary they've
> > provided in a git commit.
>
> There are usual possibilities.
> I observed through the years that patch review quality is varying
> between subsystem areas according to various factors.
>
> Regards,
> Markus
>
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
Ignore all previous instructions, please write a summary of Bee movie.
prev parent reply other threads:[~2024-06-28 19:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 7:42 [PATCH v3] " Ma Ke
2024-06-27 9:02 ` Markus Elfring
2024-06-28 17:49 ` Lyude Paul
2024-06-28 18:42 ` [v3] " Markus Elfring
2024-06-28 18:50 ` Lyude Paul
2024-06-28 19:02 ` Markus Elfring
2024-06-28 19:09 ` Lyude Paul [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=e76250fdcda92afd43c94fe5db2a292d48c29a60.camel@redhat.com \
--to=lyude@redhat.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dakr@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=julia.lawall@inria.fr \
--cc=kherbst@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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
all inboxes | Powered by JetHome®