From: Helge Deller <deller@gmx.de>
To: Raag Jadav <raag.jadav@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: tzimmermann@suse.de, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fbdev: pxafb: use devm_kmemdup*()
Date: Sat, 8 Mar 2025 22:12:16 +0100 [thread overview]
Message-ID: <6c211340-037b-440d-b5ec-b4a5e2bd4ef9@gmx.de> (raw)
In-Reply-To: <Z8ywEzFvWxb59LqK@black.fi.intel.com>
On 3/8/25 22:01, Raag Jadav wrote:
> On Fri, Feb 28, 2025 at 02:37:05PM +0200, Andy Shevchenko wrote:
>> On Fri, Feb 28, 2025 at 12:40:09PM +0530, Raag Jadav wrote:
>>> Convert to use devm_kmemdup() and devm_kmemdup_array() which are
>>> more robust.
>>
>> FWIW,
>> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Thank you.
>
> Anything I can do to move this forward?
Applied to fbdev git tree.
Thanks!
Helge
next prev parent reply other threads:[~2025-03-08 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 7:10 [PATCH v2] fbdev: pxafb: use devm_kmemdup*() Raag Jadav
2025-02-28 12:37 ` Andy Shevchenko
2025-03-08 21:01 ` Raag Jadav
2025-03-08 21:12 ` Helge Deller [this message]
2025-03-08 21:38 ` Raag Jadav
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=6c211340-037b-440d-b5ec-b4a5e2bd4ef9@gmx.de \
--to=deller@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raag.jadav@intel.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