From: Markus Elfring <Markus.Elfring@web.de>
To: Lyude Paul <lyude@redhat.com>,
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 21:02:53 +0200 [thread overview]
Message-ID: <c41b19ac-6bf9-4f30-8c00-0cf63246d825@web.de> (raw)
In-Reply-To: <eab9d109981bae8a443649bc4a2c1a08870590c7.camel@redhat.com>
> Because the responses you have been given read like a bot,
I find it interesting that you interpret provided information
in such a direction.
> 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
next prev parent reply other threads:[~2024-06-28 19:03 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 [this message]
2024-06-28 19:09 ` Lyude Paul
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=c41b19ac-6bf9-4f30-8c00-0cf63246d825@web.de \
--to=markus.elfring@web.de \
--cc=Jonathan.Cameron@Huawei.com \
--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=lyude@redhat.com \
--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®