From: "Christian König" <christian.koenig@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Dragos-Marian Panait <dragos.panait@windriver.com>,
stable@vger.kernel.org, Jiasheng Jiang <jiasheng@iscas.ac.cn>,
Felix Kuehling <Felix.Kuehling@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Oded Gabbay <oded.gabbay@gmail.com>,
Kent Russell <kent.russell@amd.com>,
Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
Date: Thu, 19 Jan 2023 12:49:02 +0100 [thread overview]
Message-ID: <25814d03-182b-a2ca-2d5f-1cb5290f5656@amd.com> (raw)
In-Reply-To: <Y8ka2khSlK6E/XbF@phenom.ffwll.local>
Am 19.01.23 um 11:26 schrieb Daniel Vetter:
> [SNIP]
> I guess next step is that people will use chatgpt to write the patches for
> these bugs.
To be honest I think that would result in quite some improvement in the
average patch quality.
That guessing this AI does has at least a statistically proven chance to
be correct.
Cheers,
Christian.
prev parent reply other threads:[~2023-01-19 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 17:56 [PATCH 5.10 0/1] drm/amdkfd: Check for null pointer after calling kmemdup Dragos-Marian Panait
2023-01-04 17:56 ` [PATCH 5.10 1/1] " Dragos-Marian Panait
2023-01-12 12:47 ` Greg KH
2023-01-12 15:26 ` Daniel Vetter
2023-01-12 16:45 ` Greg KH
2023-01-19 10:26 ` Daniel Vetter
2023-01-19 11:49 ` Christian König [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=25814d03-182b-a2ca-2d5f-1cb5290f5656@amd.com \
--to=christian.koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Harish.Kasiviswanathan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dragos.panait@windriver.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiasheng@iscas.ac.cn \
--cc=kent.russell@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oded.gabbay@gmail.com \
--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