From: Greg KH <gregkh@linuxfoundation.org>
To: Samyak <samyak.bambole07@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: vme_user: use kmalloc_obj instead of kmalloc
Date: Sat, 14 Feb 2026 17:27:57 +0100 [thread overview]
Message-ID: <2026021428-reliance-vitally-f279@gregkh> (raw)
In-Reply-To: <20260214161321.669459-1-samyak.bambole07@gmail.com>
On Sat, Feb 14, 2026 at 09:43:21PM +0530, Samyak wrote:
> From: Samyak Bambole <samyak.bambole07@gmail.com>
>
> Replace kmalloc(sizeof(*ptr), GFP_KERNEL) calls with kmalloc_obj(*ptr,
> GFP_KERNEL)
>
> This addresses scripts/checkpatch.pl warnings and follows the preffered
Nit, spelling problem in the last word :)
> allocation pattern.
>
> Signed-off-by: Samyak Bambole <samyak.bambole07@gmail.com>
>
> ---
You need to put what changed below the --- line as my bot recommends.
v3?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-14 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 16:13 [PATCH v2] staging: vme_user: use kmalloc_obj instead of kmalloc Samyak
2026-02-14 16:27 ` Greg KH [this message]
2026-02-14 16:28 ` Greg KH
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=2026021428-reliance-vitally-f279@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=samyak.bambole07@gmail.com \
/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