From: Matt Coster <Matt.Coster@imgtec.com>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Frank Binns <Frank.Binns@imgtec.com>,
Jinjie Ruan <ruanjinjie@huawei.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH -next v2] drm/imagination: Use memdup_user() helper
Date: Tue, 3 Sep 2024 09:12:37 +0000 [thread overview]
Message-ID: <cc1a5b72-2349-4b7b-b233-1a1b90556d71@imgtec.com> (raw)
In-Reply-To: <8d30da7f-7a12-4052-b846-66fad0ccb392@web.de>
[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]
On 02/09/2024 17:09, Markus Elfring wrote:
>>> Switching to memdup_user(), which combines kmalloc() and copy_from_user(),
>>> and it can simplfy code.
>>
>> Applied, thanks!
>>
>> [1/1] drm/imagination: Use memdup_user() helper
>> commit: 2872a57c7ad427d428c6d12e95e55b32bdc8e3b8
>
> Do you find any previous contributions still similarly interesting?
>
> Example:
> [PATCH] drm/imagination: Use memdup_user() rather than duplicating its implementation
> https://lore.kernel.org/r/c07221ed-8eaf-490e-9672-033b1cfe7b6e@web.de
> https://lkml.org/lkml/2024/1/28/438
Hi Markus,
I apologise for missing your earlier email. In general, we'll happily
accept cleanup patches.
If you feel like your patch has gone ignored in future, please feel free
to ping me directly either by email or on IRC at MTCoster.
Cheers,
Matt
---
Matt Coster
E: matt.coster@imgtec.com
> Regards,
> Markus
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2024-09-03 9:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 2:33 Jinjie Ruan
2024-09-02 7:59 ` Frank Binns
2024-09-02 9:21 ` Matt Coster
2024-09-02 16:09 ` Markus Elfring
2024-09-03 9:12 ` Matt Coster [this message]
2024-09-03 9:40 ` [v2] " Markus Elfring
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=cc1a5b72-2349-4b7b-b233-1a1b90556d71@imgtec.com \
--to=matt.coster@imgtec.com \
--cc=Frank.Binns@imgtec.com \
--cc=Markus.Elfring@web.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=tzimmermann@suse.de \
/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®