[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <95f07e5b-72c4-442c-b58e-25c407389243@web.de>
Date: Tue, 3 Sep 2024 11:40:11 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Matt Coster <Matt.Coster@...tec.com>, dri-devel@...ts.freedesktop.org
Cc: Donald Robson <donald.robson@...tec.com>,
Frank Binns <Frank.Binns@...tec.com>, Sarah Walker
<sarah.walker@...tec.com>, Christophe Jaillet
<christophe.jaillet@...adoo.fr>, Jinjie Ruan <ruanjinjie@...wei.com>,
Daniel Vetter <daniel@...ll.ch>, David Airlie <airlied@...il.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
LKML <linux-kernel@...r.kernel.org>, kernel-janitors@...r.kernel.org
Subject: Re: [v2] drm/imagination: Use memdup_user() helper
>>>> 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
Powered by blists - more mailing lists