From: Markus Elfring <Markus.Elfring@web.de>
To: Matt Coster <Matt.Coster@imgtec.com>, dri-devel@lists.freedesktop.org
Cc: Donald Robson <donald.robson@imgtec.com>,
Frank Binns <Frank.Binns@imgtec.com>,
Sarah Walker <sarah.walker@imgtec.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
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>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [v2] drm/imagination: Use memdup_user() helper
Date: Tue, 3 Sep 2024 11:40:11 +0200 [thread overview]
Message-ID: <95f07e5b-72c4-442c-b58e-25c407389243@web.de> (raw)
In-Reply-To: <cc1a5b72-2349-4b7b-b233-1a1b90556d71@imgtec.com>
>>>> Switching to memdup_user(), which combines kmalloc() and copy_from_user(),
>>>> and it can simplfy code.
By the way:
Would it have been nicer to avoid a typo anyhow in such a change description?
>>> 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.
How could this happen?
> In general, we'll happily accept cleanup patches.
>
> If you feel like your patch has gone ignored in future,
It seems that some of my development ideas occasionally trigger special communication challenges.
> please feel free to ping me directly either by email or on IRC at MTCoster.
Will the attention really grow accordingly?
Regards,
Markus
prev parent reply other threads:[~2024-09-03 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 2:33 [PATCH -next v2] " 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
2024-09-03 9:40 ` Markus Elfring [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=95f07e5b-72c4-442c-b58e-25c407389243@web.de \
--to=markus.elfring@web.de \
--cc=Frank.Binns@imgtec.com \
--cc=Matt.Coster@imgtec.com \
--cc=airlied@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=daniel@ffwll.ch \
--cc=donald.robson@imgtec.com \
--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=sarah.walker@imgtec.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®